The WSDL does not conform to WS-I BasicProfile 1.x because the SOAP bindings
use RPC/Literal style on message having "element" parts instead of xml
"type" parts.
To resolve this, you should either:
1) Use XML types instead of elements in the message definitions:
e.g. change,
<message name="Test4RequestMessage">
<part name="payload" element="tns:Test4Request"/>
</message>
to
<message name="Test4RequestMessage">
<part name="payload" type="tns:Test4RequestType"/>
</message>
(and convert your elements to types in the schema)
or 2) Use Document/Literal binding by changing,
<binding name="Test4SOAPBinding" type="tns:Test4">
<soap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http"; />
....
</binding>
to
<binding name="Test4SOAPBinding" type="tns:Test4">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"; />
....
</binding>
(This second option only works if your message only have a single part)
I don't know if it's an inherent problem of the BPEL Designer or if somehow
you went through the wrong path for the WSDL generation. In any case, it's
likely this WSDL would not work with the vast majority of tools out there.
cheers,
alex
