Daniel Kulp wrote:
On Mon May 11 2009 5:19:06 pm David Robertson wrote:
I'm having a problem with the attached WSDL. It is valid, but the code
generated for the operation has the output elements, unwrapped, in the
parameter list and a void return type. I don't have the option of
changing the WSDL. Is this something that can be fixed with enough
binding entries, or would the problem be manifesting before it gets to
the binding.
-David Robertson
This code is generating exactly per spec.
You could switch it to "bare" mode with a binding entry so it would not unwrap
the input or output.
"unwrapped" means just one element in the input parameter list
corresponding to the input message, and a return type corresponding to
the output message (the terminology being a little confusing)? In
wrapped, if there is an output message, there is the usage of the Holder
class and the elements of the output message are part of the input
parameters, and a void return type?
The WSDL that I provided is an excerpt. In the other operations, where
the input message name is not the same as the operation name, the
corresponding code generated is unwrapped (in the above sense if that is
correct). Is the default unwrapped for everything, or is it finer
grained than that.
-David Robertson
