You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexis Midon (JIRA)" <ji...@apache.org> on 2009/04/10 00:40:12 UTC

[jira] Updated: (ODE-577) No separate threads for ExternalServices replies

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

Alexis Midon updated ODE-577:
-----------------------------

    Description: 

SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.

Obviously the transaction is mandatory, but it does not have to happen in another thread.
So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.





  was:

SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.

Obviously the transaction is mandatory, but it does have to happen in another thread.
So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.






> No separate threads for ExternalServices replies
> ------------------------------------------------
>
>                 Key: ODE-577
>                 URL: https://issues.apache.org/jira/browse/ODE-577
>             Project: ODE
>          Issue Type: Improvement
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 1.3.1, 2.0
>
>
> SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.
> Obviously the transaction is mandatory, but it does not have to happen in another thread.
> So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.