Hello,
I guess it's not possible now, but we could fill additional information in
variable, so you could do something like this:
<scope name="scopeOne">
<faultHandlers>
<catch faultName="ext:activityRecovery"
faultVariable="testError">
to get additional information about problem.
Let me know if it would work for you and we'll create jira issue for this.
On 12 May 2010 21:51, Łukasz Budnik <[email protected]> wrote:
> Hi All,
>
> I have a problem with find out more about failure converted to fault.
>
> For example, when one of my partners in unavailable I get failure
> which says this and this service could not be reached.
>
> When I use ODE activity recovery extension and map failures to faults,
> yes, I'm able to catch fault and handle it inside WS-BPEL but I don't
> know nothing about what happened. The fault message just says activity
> failure.
>
> Is it possible to find out the root cause of such fault?
>
> thanks,
> Łukasz
>
--
Regards,
Rafał Rusin
http://rrusin.blogspot.com
