Hello Daniel,
When you use DOCUMENT/LITERAL with the "wrapped" convention, the SOAP
message will still contain a wrapper element under the body, but this
element will not be mapped to a Java class (the corresponding JavaBean
will not be generated).
If you do not use the "wrapped" convention, a wrapper class is generated
and used.
If you start with a Java interface, specify WRAPPED instead of DOCUMENT
in the option to Java2WSDL to get a WSDL with the "wrapped" convention.
If you work from the WSDL, follow the criteria in the JAX-RPC 1.1 spec
and change your WSDL. I believe WSDL2Java also has an option to ignore
the criteria and generate and use the wrapper beans anyway.
Note that for arrays (complexType with one element with maxOccurs >1)
wrapper classes are not generated by default. Use WSDL2Java's
--wrapArrays option to use wrapper classes for arrays (again, this
should not affect the SOAP message).
Regards,
Dies
Daniel Destro wrote:
Someone told me here to use DOCUMENT/LITERAL instead of ENCODED SOAP,
because I wanted a more simple SOAP response message.
Well, it does work, BUT the problem is, it no longer uses Wrapper Types,
instead it uses primitives.
Is it possible to use wrappers using literal soap style?
thanks
Daniel
