[ http://issues.apache.org/jira/browse/ODE-33?page=comments#action_12428687 ] Maciej Szefler commented on ODE-33: -----------------------------------
No, you are thinking of a different use case: resolveEndpointReference is relevant when one obtains EPR XML from a partner and needs to find the corresponding JBI ServiceEndpoint. The problem I am referring to is how to send the MyRole EPR to the partner. In this case getExternalEndpoints needs to be used to obtain the external representation of the MyRole endpoint (which as you point out is activated by some BC). If the BC has not yet registered the external endpoint at the time the BPEL engine calls getExternalEndpoints then there's a problem. That is why this call cannot be made during process activation, and should only be made right before it is required. > 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
