A business object parsing issue occurs for WebSphere Process Server (WPS) in the default SOAP data handler when MQ/JMS or JMS binding is used as the transport protocol

Technote (troubleshooting)


Problem(Abstract)

When you use the MQ/JMS binding as the transport protocol, you choose the default SOAP data handler (SOAPDataTransformationConfig) to parse the SOAP message. However, the business object in the SOAP header is not parsed. Also, if there are multiple business objects in the SOAP body, only the first business object is parsed.

Symptom

The business object in the SOAP header is not parsed and multiple business objects in the SOAP body are not parsed.


Resolving the problem

You can resolve this issue by implementing a customized SOAP data handler. For information on how to implement a customized SOAP data handler, see the Data handlers topic in the WebSphere Process Server Information Center.

Related information

A simplified Chinese translation is available

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Process Server
Data Bindings and Data Handlers

Software version:

7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4

Operating system(s):

AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, i5/OS

Reference #:

1615827

Modified date:

2012-11-12

Translate my page

Machine Translation

Content navigation