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 2010/04/13 13:00:53 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 ]

Tammo van Lessen updated ODE-479:
---------------------------------

    Fix Version/s: 1.3.5
                       (was: 1.3.4)

Postponing to 1.3.5

> 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.2
>         Environment: platform-independent
>            Reporter: Karthick Sankarachary
>             Fix For: 1.3.5
>
>
> 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.
-
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