MQSeries.net :: View topic - How to handle soap fault in message set and WSDL?

jamesyu · Posted: Thu Mar 15, 2007 4:46 pm Post subject:

Hi All,

1. In my message set, I've created 3 messages: request, response and error.
2. In my message category file, the request message is set with Role Type of "wsdl:input" and Role Usage of "soap:body". The response message is set with Role Type of "wsdl:output" and Role Usage of "soap:body". The error message is set with Role Type of "wsdl:fault" and Role Usage of "soap:fault"
3. Generated WSDL with soap over JMS with two-way operation
4. Imported WSDL to RAD, and a Web service client was generated successfully in RAD
5. Sent a valid request message via the Web service client in RAD, and a response message was retrieved from the flow successfully.

Here is how I handle invalid request messages in my flow. If the last name can't be found from the request message, I create an error message and send back to the caller instead of a positive response message. Notice that the "error" message has its own message structure which is different than the normal response message.

The thing is, such a reply message with error information can't be taken by the Web service client in RAD at all with the following Java exception occurred:

"org.xml.sax.SAXException: WSWS3047E: Error: Cannot deserialize element id of bean com.thc.broker.webservice.Lab_info."

Notice that, the element "id" is the first element defined in my error message structure. The "Lab_info" message is my actual request message.

In my case, I treated the error message exactly like a normal response message, just with different message structure and content.

Does that imply I can't have a separate message created to handle the errors in the message set?

how is the soap:fault/wsdl:fault being handled in the message category and WSDL in broker?

Thanks,
James