You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexis Midon (JIRA)" <ji...@apache.org> on 2009/04/18 01:26:15 UTC
[jira] Updated: (ODE-479) Evaluate Exit Activity Eagerly
[ https://issues.apache.org/jira/browse/ODE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-479:
-----------------------------
Fix Version/s: (was: 1.3.1)
1.3.2
> Evaluate Exit Activity Eagerly
> ------------------------------
>
> Key: ODE-479
> URL: https://issues.apache.org/jira/browse/ODE-479
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.1
> Environment: platform-independent
> Reporter: Karthick Sankarachary
> Fix For: 1.3.2
>
>
> As per section 10.10 of the BPEL 2.0 specification, a business process instance must evaluate the <exit> activity eagerly (as opposed to lazily). In particular, it must forcefully terminate all other running or pending activities, no questions asked.
> It has been insinuated that the implementation of the <exit> activity might not be as eager as it ought to be. This calls for a review of that piece of code, specifically to make sure that the reaction queue is flushed in a timely manner.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.