1) Do we need to implement Exception Handling in BPEL as we do in Java, means
method 3 throws error to method 2 (if any) and
method 2 throws error to method 1 (if any) and
finally method 1 throws error to the main Class.

If we replicate the above scenairo to BPEL

In BPEL main Scope have Custom Fault, Catch ALL

At each Invoke’s surrounded by a Scope Acitivity with Remote Fault, Binding Fault & Custom Fault

[or]

2) In BPEL main Scope have all exceptions defined like
Remote Fault,
Binding Fault,
anyOther System Fault,
Custom Fault (if required) and
CatchALL

and also
each Invoke is surrounded by a Scopes Acitivity with Custom Fault (business fault) exception Handling

I’m doing a lot integration projects lately and we noticed implementing good eror handling functionality takes a lot of time. Mostly these parts are also not well planned in the projects. For integration components it’s hard to have good error handling functionality because reaches a lot of components and environments. Every possible error can also have it’s own handling functionality. Integration components like bpels could make use of compensation handlers but in java you would try to handle it which the exceptions, and other components could have their own strategies for those situations. So…it’s hard to describe one generic error handling strategy which applies all.But for sure it’s important to ‘think more’ about error handling’

I am running into the same problem with flex, there is also a fault mechanism with events implemented. But you do not have the capabilities of java available to handle the events in a standard way. You can create a mechanism yourself, but for bigger appications that is not what you want.

Error handling keeps being one of 4 attention points for projects: configuration management, application layering, standardized package, class and method names and error handling.

thanks for the article.