You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Maciej Szefler (JIRA)" <ji...@apache.org> on 2006/08/17 17:19:14 UTC
[jira] Created: (ODE-33) Obtaining the "initial" EPR for a partner
link should be done as lazyly as possible.
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
[jira] Resolved: (ODE-33) Obtaining the "initial" EPR for a partner
link should be done as lazyly as possible.
Posted by "Maciej Szefler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/ODE-33?page=all ]
Maciej Szefler resolved ODE-33.
-------------------------------
Resolution: Fixed
Latest IAPI makes lazy look-ups possible.
> 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
[jira] Commented: (ODE-33) Obtaining the "initial" EPR for a
partner link should be done as lazyly as possible.
Posted by "Maciej Szefler (JIRA)" <ji...@apache.org>.
[ 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
[jira] Closed: (ODE-33) Obtaining the "initial" EPR for a partner
link should be done as lazyly as possible.
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou closed ODE-33.
----------------------------
> Obtaining the "initial" EPR for a partner link should be done as lazyly as possible.
> ------------------------------------------------------------------------------------
>
> Key: ODE-33
> URL: https://issues.apache.org/jira/browse/ODE-33
> Project: 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-33) Obtaining the "initial" EPR for a
partner link should be done as lazyly as possible.
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/ODE-33?page=comments#action_12428711 ]
Alex Boisvert commented on ODE-33:
----------------------------------
As a matter of architecture, it's usually better to pass EPRs that are universally accessible (e.g. HTTP endpoints) over EPRs that are limited to specific environments (e.g. JBI endpoints) because you never know how far the EPRs will travel in a service composition architecture, or who's going to receive your EPRs.
Put another way, I would see it as a responsibility of the JBI container or binding components to optimize invocations whenever possible by recognizing that connection paths are available in-VM or through more efficient transports.
Plus, it avoids all kind of problems on the sender side such as having to decide which EPR or endpoint to send to another service.
> 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
[jira] Commented: (ODE-33) Obtaining the "initial" EPR for a
partner link should be done as lazyly as possible.
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (ODE-33) Obtaining the "initial" EPR for a
partner link should be done as lazyly as possible.
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/ODE-33?page=comments#action_12428691 ]
Guillaume Nodet commented on ODE-33:
------------------------------------
Oh, sorry. Sounds good.
But how / when is the MyRole EPR sent to the partner ?
Also, if the partner is another JBI service, the use of the external endpoint may be a problem.
> 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
[jira] Commented: (ODE-33) Obtaining the "initial" EPR for a
partner link should be done as lazyly as possible.
Posted by "Maciej Szefler (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (ODE-33) Obtaining the "initial" EPR for a
partner link should be done as lazyly as possible.
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/ODE-33?page=comments#action_12428723 ]
Guillaume Nodet commented on ODE-33:
------------------------------------
Agreed
> 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