(Deprecated) Requirements for BPEL processes in JMS-based client applications (deprecated)
BPEL processes developed with IBM® Integration Designer to run on Business Process Choreographer must conform to specific rules to be accessible through the JMS API.
Attention: The Business Process Choreographer
JMS API is deprecated. To develop JMS-based client applications, use
the Business Process Choreographer web services API with the SOAP/JMS
transport protocol.
The requirements are:
- The interfaces of BPEL processes must be defined using the "document/literal wrapped" style defined in the Java™ API for XML-based RPC (JAX-RPC 1.1) specification. This is the default style for all BPEL processes and human tasks developed with Integration Designer.
- Fault messages exposed by BPEL processes and human tasks for web
service operations must comprise a single WSDL message part defined
with an XML Schema element. For example:
<wsdl:part name="myFault" element="myNamespace:myFaultElement"/>