From DeveloperWorks, Handling unmodeled faults within WebSphere Process Server V6.1

See how BPEL processes can handle unmodeled faults with a user-defined fault handler by using SCA mediation module (ESB) capabilities.

In this article, they talk about handling a scenario where a WSDL SOAP/HTTP service does not define any faults but actually lands up throwing one (StockNoExist). Now, what I would normally do is just edit the WSDL definition used by the BPEL to include the fault definition. This technically works even though the source and target wsdls are different (the fault definition). If you want (or can't) touch the wsdl then you have to follow the steps in this article to make catching the specific error possible.

Related Posts

• Error Handling in WebSphere Process Server: Developing an Error Handling Strategy
• WebSphere Process Server and RPC/Literal Web Services: Beware Messages defined by ‘type’ instead of ‘element’.
• WebSphere Integration Developer - Namespaces Cannot Span Projects
• WebSphere Enterprise Service Bus - Mediation Flow Component: No Refactoring for WSDL Faults
• WebSphere Process Server Endurance

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.