[jira] Updated: (ODE-599) Enable concurrent execution of Invoke in in-memory processes

["Tammo van Lessen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ODE-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tammo van Lessen updated ODE-599:
---------------------------------

    Fix Version/s: 1.3.5

> Enable concurrent execution of Invoke in in-memory processes
> ------------------------------------------------------------
>
>                 Key: ODE-599
>                 URL: https://issues.apache.org/jira/browse/ODE-599
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime, Deployment
>    Affects Versions: 2.0
>            Reporter: Jürgen Schumacher
>             Fix For: 1.3.5
>
>         Attachments: async-invoke.patch
>
>
> In ODE 2.0 (beta2), Invoke activities in Flow activities are not executed concurrent, but in random order.
> See thread in dev list at http://mail-archives.apache.org/mod_mbox/ode-dev/200904.mbox/%3c653C8E101491144F9B644FFA6652F5E5010AC88F@gtlbmlexs0006.bagmail.net%3e for details.
> The attached patch adds an <async-invoke> option to the deploy.xml schema. Default is false in order to keep current behaviour for backward compatibility. If set to true, the engine will treat Invoke activities in transient processes asynchronously exactly as in persistent processes, to that they in Flow activities they are called concurrently.
> I've created the patch in the current trunk source code, your junit test cases seem to be OK. To test the functionality, I've also applied it to the ODE 2.0-beta2 source and used it in the integration of ODE in SMILA, where it worked as described.
> If you want something to be changed, just tell me.

-- 
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