Example:
In the schema:
<element name="importDocumentResponse" type="impl:emptyResponse_t"/>
<complexType name="emptyResponse_t">
<sequence/>
</complexType>
In the WSDL:
<wsdl:message name="importDocumentRequest">
<wsdl:part name="parameters" element="impl:importDocument"/>
</wsdl:message>
<wsdl:message name="importDocumentResponse">
<wsdl:part name="parameters" element="impl:importDocumentResponse"/>
</wsdl:message>
will generate with JWSDP 1.5 a method like this:
public emptyResponse_t operation(...);
but expect:
public void operation(...);
Without a workaround that's mean that WSDP and .NET are not interoperable when using Wrapped-Document/Literal.
A search of file *.wsdl inside the package of JWSDP 1.5 return 0 file, probably meaning that WSDP goal is not to drive Web Services design and contract by a WSDL.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net