Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Dealing With Expected and Unexpected Faults in BPEL

DZone's Guide to

Dealing With Expected and Unexpected Faults in BPEL

Free Resource

Learn how to troubleshoot and diagnose some of the most common performance issues in Java today. Brought to you in partnership with AppDynamics.

In BPELs in WebSphere Integration Developer we can catch exceptions – faults from a BPEL, like during an invoke for example.

image

What happens when we want to catch an exception that is not necessarily a fault and could stem from the underlying  system or the application behind the invoke(in the diagram it is InvokeSomeOperation)?

As you can see in the above excerpt of a BPEL, we have a known Fault called MyApplicationFault in the catch and then in the Catch All we deal with any unknown faults that are not MyApplicationFault and just exceptions that are not BPEL faults at all.

So if we have a NumberFormatException for example it will pass the MyApplicationFault catch and go the Catch All.

Now if we want to transform any exception that comes through in a BPEL exception that will be like a fault we can use an anonymous class in a snippet:

new BpelException(){

    public String getFaultName() {

    return “MyFaultName”;

    }

    public String getMessage() {

    return caughtException.getMessage();

    }

};

 

This way we can handle the exception elsewhere in the BPEL Process using:

com.ibm.bpe.api.BpelException bpelexception = getCurrentFaultAsException();

logger.debug(“Fault Name” + bpelexception.getFaultName());

bpelexception.printStackTrace( System.out);

Throwable rootCause = bpelexception.getRootCause();

So the Catch All can accept normal java exceptions as well as BPEL faults Smile

 

From http://gabrieljeremiahcampbell.wordpress.com/2012/02/29/catching-expected-and-unexpected-faults-in-bpel/

Understand the needs and benefits around implementing the right monitoring solution for a growing containerized market. Brought to you in partnership with AppDynamics.

Topics:

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}