Open glassfishrobot opened 9 years ago
We have a WSDL which contains the following:
<wsdl:message name="RequestMetadata"> <wsdl:part element="x2tc:RequestMetadata" name="metadata" /> </wsdl:message> <wsdl:message name="CreateOfferProjectStructure"> <wsdl:part element="ns:CreateOfferProjectStructure" name="offerProjectStructure" /> </wsdl:message> ... binding: <wsdl:input> <soap:header use="literal" part="metadata" message="tns:RequestMetadata" /> <soap:body use="literal" /> </wsdl:input>
After SEI generation and endpoint publication the JAX-WS generated WSDL collapses both into one message:
<message name="CreateOfferProjectStructure"> <part xmlns:ns1="..." name="offerProjectStructure" element="ns1:CreateOfferProjectStructure"/> <part xmlns:ns2="..." name="metadata" element="ns2:RequestMetadata"/> </message>
Though, this is perfectly valid and conform BP 1.2 R2208, SAP WAS ABAP proxy generator is not able to handle messages without a part or more than one part.
The generation should be controllable or should leave messages as-is.
[2.2.8]
Reported by michael-o
This issue was imported from java.net JIRA JAX_WS-1158
We have a WSDL which contains the following:
After SEI generation and endpoint publication the JAX-WS generated WSDL collapses both into one message:
Though, this is perfectly valid and conform BP 1.2 R2208, SAP WAS ABAP proxy generator is not able to handle messages without a part or more than one part.
The generation should be controllable or should leave messages as-is.
Affected Versions
[2.2.8]