You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rafal Rusin (JIRA)" <ji...@apache.org> on 2009/05/25 13:13:45 UTC
[jira] Created: (ODE-612) ActivityRecovery failureOnFault
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
Fix For: 1.3.3
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.
[jira] Updated: (ODE-612) ActivityRecovery failureOnFault
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert updated ODE-612:
------------------------------
Fix Version/s: (was: 1.3.3)
1.3.4
> 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.4
>
> 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.
[jira] Commented: (ODE-612) ActivityRecovery failureOnFault
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (ODE-612) ActivityRecovery failureOnFault
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin updated ODE-612:
----------------------------
Priority: Minor (was: Major)
> 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.
[jira] Resolved: (ODE-612) ActivityRecovery failureOnFault
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin resolved ODE-612.
-----------------------------
Resolution: Won't Fix
> 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.4
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ODE-612) ActivityRecovery failureOnFault
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin updated ODE-612:
----------------------------
Attachment: failureOnFault.diff
test.zip
Attached are implementation and a test example for JBi version.
> 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
> 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.
[jira] Commented: (ODE-612) ActivityRecovery failureOnFault
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12717980#action_12717980 ]
Rafal Rusin commented on ODE-612:
---------------------------------
Right, extvar are treated as failures, I was wrong.
So the remaining use case for it is for invokes.
> 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.