Not all web servers are configured to handle SOAP messages containing CoordinationContext elements. You can use WebSphere® Application Server to configure a custom property for the compensation service which processes a predefined list of Enterprise Java Beans for which no CoordinationContext should be sent on web service requests.
<wscoor:CoordinationContext soapenv:mustUnderstand="1" ... </wscoor:CoordinationContext>If such a SOAP message is received by a web server which is not configured to process CoordinationContext elements, an exception message is produced. See the following example:
Header block local name 'CoordinationContext' is not defined.
application_name#module#bean application_name#module#bean application_name#module#beanHere application_name is the name of the application as known on the server; module is the name of the Enterprise Java Bean jar; and bean is the name of the Enterprise Java Bean.
Web service requests sent from Enterprise Java Beans listed in the custom property file will not contain CoordinationContext metadata in the outgoing SOAP message header.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |