Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.0-incubating
-
None
Description
Apparently, the complex type wrapper element <xsd-complex-type-wrapper/> is visible in message sent by the engine.
In this case, we have a message definition:
<message name="createTaskRequest">
<part name="wipart" type="tns:StringArray"/>
</message>
with complex type:
<complexType name="StringArray">
<sequence>
<element name="item" type="xsd:string" minOccurs="0" maxOccurs="unbounded" />
</sequence>
</complexType>
leading to this response:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header/>
<soapenv:Body>
<axis2ns8:testItResponse xmlns:axis2ns8="http://ode/bpel/unit-test.wsdl">
<wipart>
<xsd-complex-type-wrapper> <!-- ????? --->
<tm:item xmlns:tm="urn:TaskManager">test1text</tm:item>
<tm:item xmlns:tm="urn:TaskManager">test2text</tm:item>
</xsd-complex-type-wrapper> <!-- ????? --->
</wipart>
</axis2ns8:testItResponse>
</soapenv:Body>
</soapenv:Envelope>