Hello Terry, I was also looking at this place :) there is actually an if clause in following lines which is checking wherever p2pProcesses is not null, so if you would comment out this part may be you should also delete the whole If statement, however before I would propose to discuss a different options. Actually in the ODE documentation P2P communication is described as a feature, not as a bug. It's obviously better from the reliability point of view that one process sending a message to another process reliably and no exceptions could happen there, however sometimes it's better that integration layer would do this "shortcut" instead of delegating it to ODE core. Another possible solution would be to determine routing rule not based on the Service QName but on the Port Name (or QName with WSDL TNS) so that if any of the deployed processes implements a given Port (not Service) then do a shorcut.
Renat On 04.02.10 09:20, "Terry Mueller" <[email protected]> wrote: +1 I've commented out the following lines in ODEWSProcess.java to get this to work: // if (partnerEndpoint != null) // p2pProcesses = _server.route(partnerEndpoint.serviceName, new DbBackedMessageImpl(mexdao.getRequest())); Regards, Terry On 03/02/10 22:34, Renat Zubairov wrote: > 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 > >
