It appears part of my WSDL definition was lost. Here it is:
<message name="getAllInput"/> <message name="getAllInput"/> <message name="getAllOutput"> <part name="result" element="service:getAllResponse"/> </message> <portType name="actionItemPort"> <operation name="getAll"> <input message="service:getAllInput"/> <output message="service:getAllOutput"/> </operation> </portType>
Maybe this is an issue with ananomous schema types. You could try
<xs:complexType name="GetAllResponseType"> <xs:sequence> <xs:any namespace="http://iss.lmco.com/schema/action-item-summary" maxOccurs="1"/> </xs:sequence> </xs:complexType> <xs:element name="getAllResponse" type="schema:GetAllResponseType">
Thank you for your response. Unfortunately, switching from anonymous types did not help the situation. WSCOMPILE still unwraps the type containing only an xsd:any element.
If anyone has other suggestions, I would appreciate it. Otherwise, who or what organization should I contact about a potential bug within WSCOMPILE if it truely is a bug?
For those who are curious, I found the solution to the issue I was having.
JAXRPC 1.1 does not support xsd:any with a specified namespace. It only supports the namespace values of ##any and ##other. When I used one of those values, the appropriate Java class was generated by wscompile. JAXRPC 2.0 will support a specified namespace.