[ 
https://issues.apache.org/jira/browse/ODE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846919#action_12846919
 ] 

Hudson commented on ODE-758:
----------------------------

Integrated in ODE-1.x #83 (See 
[http://hudson.zones.apache.org/hudson/job/ODE-1.x/83/])
    : Test case


> Disable Process2Process communication
> -------------------------------------
>
>                 Key: ODE-758
>                 URL: https://issues.apache.org/jira/browse/ODE-758
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.3.3, 2.0-beta3
>            Reporter: Terry Mueller
>            Assignee: Rafal Rusin
>         Attachments: P2PDemo.zip
>
>
> Hello all,
> I have a problem with the Process2Process communication inside the ODE. 
> Basically I need to implement a BPEL process that uses and implements the 
> same WSDL. For example I have a service A with two methods request-response 
> "createEntity" and one way "confirmCreation", I expect my process to call 
> "createEntity" method and then wait untill the "confirmCreation" method will 
> be called on it, however since ODE route all MEXes internaly despite the fact 
> that process actually only implements one single operation "confirmCreation" 
> I'm getting an MEX expire and failed state.
> Would it be possible to fix the P2P communication so that it would only 
> happen when ODE as a recipient side is able to handle the operation, 
> otherwise just proceed with a call though Integration Layer.
> Renat

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

Reply via email to