You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/05/25 18:42:45 UTC

[jira] Commented: (ODE-612) ActivityRecovery failureOnFault

    [ https://issues.apache.org/jira/browse/ODE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712749#action_12712749 ] 

Alex Boisvert commented on ODE-612:
-----------------------------------

External variable errors should always be failures.  Do you have a case where it produces a fault?  If so, please open a separate issue for that.

> ActivityRecovery failureOnFault
> -------------------------------
>
>                 Key: ODE-612
>                 URL: https://issues.apache.org/jira/browse/ODE-612
>             Project: ODE
>          Issue Type: New Feature
>          Components: BPEL Runtime
>            Reporter: Rafal Rusin
>            Priority: Minor
>             Fix For: 1.3.3
>
>         Attachments: failureOnFault.diff, test.zip
>
>
> It's nice to have a switch failureOnFault similar to faultOnFailure. 
>      <ext:failureHandling xmlns:ext="http://ode.apache.org/activityRecovery">
>         <ext:failureOnFault>true</ext:failureOnFault>
>       </ext:failureHandling>
> It's helpful when:
> - there are external variables errors (like constraint violations) and we want to repeat operation
> - we want to treat invoke fault responses as failures (to repeat)

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