[
https://issues.apache.org/jira/browse/ODE-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn updated ODE-689:
-------------------------
Description:
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.
was:
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), construct the response and send 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.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
