0
Currently I have 2 webservices running in hospitals that work perfectly with STYLE RPC/ENCODED but we will implement in a software for a factory and there they have problem to consume this type of service.
It turns out that when switching to DOCUMENT/LITERAL simply nothing happens, there is nothing in the upload header and not in the return header. I tried to use soapUI but it only says that has an error in WSDL and remains blank.
After a lot of research I came to the conclusion that it did not accept a complexType with SOAP-REF:arrayType which is where I can use an associative array.
Also after much research I found this topic: http://www.ibm.com/developerworks/library/ws-whichwsdl/#listing6
which shows a WSDL structure with DOCUMENT/LITERAL style and the difference for my structured today is that I can’t encapsulate the element the way it’s done in the example:
<element name="myMethod">
<complexType>
<sequence>
<element name="x" type="xsd:int"/>
<element name="y" type="xsd:float"/>
</sequence>
</complexType>
</element>
<element name="myMethodResponse">
<complexType/>
</element>
What I can do is create complexType and reference in the element more or less like this:
<element name='Pedido' type='tns:LayoutPedido' />
<complexType name='layoutPedido'>
<all:sequence>
<element name='id' type='xsd:string' />
</all:sequence>
</complextType>
what I can not say if it is disturbing the reading of the same.
Sorry I can’t post the original WSDL.
Why can’t post the original WSDL?
– Marcelo Bezerra bovino