[ http://issues.apache.org/jira/browse/ODE-33?page=comments#action_12428708 ] Maciej Szefler commented on ODE-33: -----------------------------------
The partnerlink's myrole can be assigned to a normal variable which can then be sent via invoke to a partner. Now the JBI partner problem: known problem, it seems we need to have an extra deployment property in JBI integration layer to control which epr internal or external is used. Another alternative is to interpret the endpoint name in the deployment descriptor a bit differently, e.g.: * always activate myrole endpoint in JBI with endpoint name "jbi" * if myrole is assigned endpoint (foo:bar,baz) then that is that endpoint that will be sent to partners (hopefully some BC has registered an external endpoint (foo:bar,baz) * when talking to "native" jbi partners, assign endpoint (foo:bar,jbi) to myrole, then the JBI internal EPR will be sent In this scenario we could avoid getExternalEndpoints, and just use getEndpoint(..) > Obtaining the "initial" EPR for a partner link should be done as lazyly as > possible. > ------------------------------------------------------------------------------------ > > Key: ODE-33 > URL: http://issues.apache.org/jira/browse/ODE-33 > Project: Apache Ode > Issue Type: Bug > Components: BPEL Runtime > Environment: JBI > Reporter: Maciej Szefler > > At the moment, the initial EPR assigned to a partner link is resolved at the > time when the process is instantiated in memory (i.e. registered with the > BpelEngineImpl). This does not work in the JBI setting where the > getExternalEndpoint method is used to obtain an EPR that a partner could > understand. The problem is that the Service Unit that exposes the external > endpoint may not have been started by the time the BPEL process service unit > is started. If this happens then the initial EPR cannot be correctly > configured. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
