You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2009/05/28 00:17:45 UTC

[jira] Assigned: (ODE-548) Error Message of Extension Activities get lost

     [ https://issues.apache.org/jira/browse/ODE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tammo van Lessen reassigned ODE-548:
------------------------------------

    Assignee: Tammo van Lessen

> Error Message of Extension Activities get lost
> ----------------------------------------------
>
>                 Key: ODE-548
>                 URL: https://issues.apache.org/jira/browse/ODE-548
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 2.0
>         Environment: any
>            Reporter: Jürgen Schumacher
>            Assignee: Tammo van Lessen
>            Priority: Minor
>             Fix For: 2.0
>
>
> I have a question concerning the handling of errors in extension activities, 
> Tammo told me to create an issue for this:
> Currently I use extensionContext.completeWithFault(Throwable) when 
> my extension activity fails. But the complete MessageExchange with 
> the BPEL process is then always completed with AckType FAILURE, 
> failure type NO_RESPONSE and explanation "Process completed without 
> responding", but no further details (like the exception message) 
> seem to be returned. I've done a bit code reading and found these lines in
> BpelRuntimeContextImpl.noreply(...):
>             mexDao.setFailureType(FailureType.NO_RESPONSE);
>             if (optionalFaultData != null) {
>                 mexDao.setFaultExplanation(optionalFaultData.toString());
>             }
>             mexDao.setFaultExplanation("Process did not respond.");
> So first my error explanation is set and then immediately overwritten again.
> Is this really intended this way? Or is there maybe just an "else" missing?
> (hopefully ;-)
> Cheers,
> Juergen

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.