This content has been marked as final. Show 1 reply
The WS-I Basic Profile v1.0 describes how many wsdl:part elements are permitted or required for document-literal and rpc-literal bindings and how they must be defined:
<ul><li> An rpc-literal binding in a DESCRIPTION MUST refer, in its soapbind:body element(s), only to wsdl:part element(s) that have been defined using the type attribute.</li>
<li>For document-literal bindings, the Profile requires that at most one part, abstractly defined with the element attribute, be serialized into the soap:Body element.</li></ul>
wscompile focuses on supporting WS-I BP compliant definitions; for non-compliant ones, it sometimes behaves strangely. If you change the binding style from rpc to document, wscompile should be able to generate the class for you.
However, jBPM BPEL does not support publishing ports with doc-literal bindings (it does support invoking them, tough). Would you please file a JIRA feature request for this?