-
1. Re: xsd:any: content of _any not present in SOAP message ret
thomas.diesler Jun 14, 2005 3:24 AM (in response to bgrieder)This has been assigned to
http://jira.jboss.com/jira/browse/JBWS-248 -
2. Re: xsd:any: content of _any not present in SOAP message ret
grp_eee Dec 27, 2005 6:12 AM (in response to bgrieder)Hi Thomas,
I face the same issue with JBoss 4.0.3 too.
Is the fix for this not available in JBoss 4.0.3 ? Is there any work around for this in JBoss 4.0.3.
Another issue which I came across is (request to) xsd:any works only if it is mapped to SOAPElement[] array even if we want to use a single element (maxOccurs=1) . Else it gives an IllegalArgumentException.
Any idea?
Any pointers on these would be really helpful.
Thanks,
Ram -
3. Re: xsd:any: content of _any not present in SOAP message ret
omatzura Dec 27, 2005 6:36 AM (in response to bgrieder)Hi!
maybe you could use the -f:nodatabinding option of wscompile which will create a method-signature taking/returning a singe SOAPElement for the entire request/response.. !?
regards!
/Ole -
4. Re: xsd:any: content of _any not present in SOAP message ret
grp_eee Dec 27, 2005 8:20 AM (in response to bgrieder)Hi,
Thanks for the response.
Actually when i run wscompile against xsd:any element it correctly creates SOAPElement or SOAPElement[] depending on the maxOccurs value.
I think the problem is not with this.According to what I found, JBoss JAX-RPC internally tries to deserialize any xsd:element into an array of SOAPElements[] and tries to invoke your set_any(SOAPElement e)
of the request object; which would raise an exception.
So this mandates us to use array of SOAPElement always.
Anyways, I am more concerned with the other issue ( same as explained in the first message) - 'could not return content of xsd:any to webservice client ' which i have come across in JBoss 4.0.3.
Any idea/information on this?
Thanks,
-Ram -
5. Re: xsd:any: content of _any not present in SOAP message ret
jason.greene Dec 27, 2005 4:36 PM (in response to bgrieder)The fix for http://jira.jboss.com/jira/browse/JBWS-248, will be included in 4.0.4.