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 2013/08/28 20:24:54 UTC

[jira] [Commented] (ODE-181) Process termination and termination handlers

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

Tammo van Lessen commented on ODE-181:
--------------------------------------

For the record, from the BPEL 2.0 spec

{code}
10.10. Immediately Ending a Process – Exit
The <exit> activity is used to immediately end the business process instance. All currently running activities MUST be ended immediately without involving any termination handling, fault handling, or compensation behavior.
{code}
                
> Process termination and termination handlers
> --------------------------------------------
>
>                 Key: ODE-181
>                 URL: https://issues.apache.org/jira/browse/ODE-181
>             Project: ODE
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Matthieu Riou
>             Fix For: 2.0
>
>
> When a process ends, either because it's completed or because we've hit an <exit/> activity, we simply end the Jacob reduction loop. In case of termination, that means that termination handlers aren't fired (haven't really tried it but can't see how it could be otherwise). Termination should be handled a nit more cleanly by actually giving a chance to the termination channel to get used.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira