3 Replies Latest reply on Apr 10, 2006 6:00 PM by thomas.diesler

JBoss404CR2 not generating xsi:nil values anymore

kdeboer Mar 13, 2006 11:32 AM

I don't know if this is already known:
My testcases on the the JBoss404CR2 build fail because the application client does no longer insert empty elements with xsi:nil (elements are optional in the wsdl and complex types (arrays) ) in the soap message while the JAXB parser on the server expects them.

Karl

1. Re: JBoss404CR2 not generating xsi:nil values anymore

lafr Mar 13, 2006 4:59 PM (in response to kdeboer)

I encountered the same problem here, using gsoap 2.7.6e for building the client app and the currenct cvs scheckout for JBoss 4.0.4.CR2.
Most elements in the wsdl file are marked as nillable=true. The wsdl and the mapping file is generated with wscompile 1.6.
The c++ variables are not set (==NULL), so the soap mesage doesn't include the element.
The validation of the message in org.jboss.xb.* gives an error/excpetion that the element was not found in the xml fragment.
Using JBoss 4.0.4.CR1 with org.jboss.axis.* the webservice communication worked perfect.
Actions
2. Re: JBoss404CR2 not generating xsi:nil values anymore

kdeboer Mar 14, 2006 3:41 AM (in response to kdeboer)

My scenario is the same. The only diffrence being that I started with the WSDL and used WSCompile 1.6 to generate the stub code and jaxrpc_mapping file

Karl
Actions
3. Re: JBoss404CR2 not generating xsi:nil values anymore

thomas.diesler Apr 10, 2006 6:00 PM (in response to kdeboer)

Please show us the schema and the soap message on the wire.

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQJIRA
Actions

Go to original post