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:12 UTC

[jira] Updated: (ODE-782) Incorrect Process2Process communication

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

Tammo van Lessen updated ODE-782:
---------------------------------

    Fix Version/s: 1.3.5

> Incorrect Process2Process communication
> ---------------------------------------
>
>                 Key: ODE-782
>                 URL: https://issues.apache.org/jira/browse/ODE-782
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.3.3, 2.0-beta2
>            Reporter: Christian Connert
>            Assignee: Rafal Rusin
>             Fix For: 1.3.5
>
>         Attachments: ODEProcess.java.patch, ODEProcess.java.patch
>
>
> Hi,
> This problem is somehow related to ODE-758. I've a one BPEL process which implements two WSDL portTypes. The process is deployed separately at two tomcat servers. Inside the deployment descriptor (deploy.xml) I bound the partnerLinks to the remote and local process. When I invoke, inside the first process, an operation of the second WSDL portType at the remote process, ODE uses the internal Process2Process allthough the partnerlink points to an external location. Thus the message is actually never sent to the second tomcat. Fortunately I found a easy way to fix this problem and appended the corresponding patch.
> Greetings 

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