You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ode.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2006/08/17 17:32:15 UTC

[jira] Commented: (ODE-33) Obtaining the "initial" EPR for a partner link should be done as lazyly as possible.

    [ http://issues.apache.org/jira/browse/ODE-33?page=comments#action_12428680 ] 
            
Guillaume Nodet commented on ODE-33:
------------------------------------

The JBI component should not use getExternalEndpoints.
External endpoints are usually activated by BC for consumer endpoints, for example a soap BC which will accept incoming http request can activate an external endpoint.
To resolve EPRs, one should use ComponentContext.resolveEndpointReference.

> 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