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 14:29:03 UTC

[jira] Updated: (ODE-689) Take out the third transaction that loads up the my role mex and related data

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

Tammo van Lessen updated ODE-689:
---------------------------------

    Fix Version/s: 1.3.5

> Take out the third transaction that loads up the my role mex and related data
> -----------------------------------------------------------------------------
>
>                 Key: ODE-689
>                 URL: https://issues.apache.org/jira/browse/ODE-689
>             Project: ODE
>          Issue Type: Improvement
>          Components: BPEL Runtime
>            Reporter: Sean Ahn
>            Assignee: Sean Ahn
>            Priority: Minor
>             Fix For: 1.3.5
>
>         Attachments: ode-689.patch.txt
>
>
> Currently, there are at least 3 transactions per a request:
> 1. Creates and persists a mex from the integration layer thread(HTTP thread)
> 2. Runs the process instance on the JACOB threads
> 3. Loads up the mex and related data(response), constructs the SOAP response and sends it back to the client(HTTP thread)
> We can remove the 3rd transaction with minimum effort by sending back the MyRoleMessageExchange object through the ResponseCallback object.

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