You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Rich Taylor <bh...@gmail.com> on 2007/11/15 02:29:12 UTC
Purely dynamic endpoints and deploy.xml?
Is it possible to have a process that invokes an operation on an
endpoint that isn't even known at deployment time with ODE?
For example a process that invokes a call to a third party service
registry to obtain an endpoint reference for a service (i.e.
PurchaseBooks), then uses that endpoint reference to invoke an
operation on the service (PurchaseBooks). There would be a
partnerlink defined for both endpoints, but the endpoint/URL for the
service (PurchaseBooks) would not be known until runtime. If this is
even possible, what would this look like in deploy.xml since the
partnerlink couldn't be bound to an endpoint at deploy time?
I read through the following and looked at the DynPartnerExample but
can't seem to figure it out.
http://ode.apache.org/user-guide.html#UserGuide-ManipulatingEndpoints
If this is unclear I can try to create an actual process that does
what I'm talking about.
Thanks, Rich
Re: Purely dynamic endpoints and deploy.xml?
Posted by Rich Taylor <bh...@gmail.com>.
Exactly the answer I was looking for. Thank you. Rich
On Nov 15, 2007 5:46 AM, Alex Boisvert <bo...@intalio.com> wrote:
> Hi Rich,
>
> Yes it's possible. You need to use initializePartnerRole='false' on the
> <partnerLink> definition, omit the partnerLink role in deploy.xml, and make
> sure you assign an endpoint reference value into the partnerLink before the
> <invoke> ;)
>
> alex
>
>
> On 11/14/07, Rich Taylor <bh...@gmail.com> wrote:
> >
> > Is it possible to have a process that invokes an operation on an
> > endpoint that isn't even known at deployment time with ODE?
> >
> > For example a process that invokes a call to a third party service
> > registry to obtain an endpoint reference for a service (i.e.
> > PurchaseBooks), then uses that endpoint reference to invoke an
> > operation on the service (PurchaseBooks). There would be a
> > partnerlink defined for both endpoints, but the endpoint/URL for the
> > service (PurchaseBooks) would not be known until runtime. If this is
> > even possible, what would this look like in deploy.xml since the
> > partnerlink couldn't be bound to an endpoint at deploy time?
> >
> > I read through the following and looked at the DynPartnerExample but
> > can't seem to figure it out.
> > http://ode.apache.org/user-guide.html#UserGuide-ManipulatingEndpoints
> >
> > If this is unclear I can try to create an actual process that does
> > what I'm talking about.
> >
> > Thanks, Rich
> >
>
Re: Purely dynamic endpoints and deploy.xml?
Posted by Alex Boisvert <bo...@intalio.com>.
Hi Rich,
Yes it's possible. You need to use initializePartnerRole='false' on the
<partnerLink> definition, omit the partnerLink role in deploy.xml, and make
sure you assign an endpoint reference value into the partnerLink before the
<invoke> ;)
alex
On 11/14/07, Rich Taylor <bh...@gmail.com> wrote:
>
> Is it possible to have a process that invokes an operation on an
> endpoint that isn't even known at deployment time with ODE?
>
> For example a process that invokes a call to a third party service
> registry to obtain an endpoint reference for a service (i.e.
> PurchaseBooks), then uses that endpoint reference to invoke an
> operation on the service (PurchaseBooks). There would be a
> partnerlink defined for both endpoints, but the endpoint/URL for the
> service (PurchaseBooks) would not be known until runtime. If this is
> even possible, what would this look like in deploy.xml since the
> partnerlink couldn't be bound to an endpoint at deploy time?
>
> I read through the following and looked at the DynPartnerExample but
> can't seem to figure it out.
> http://ode.apache.org/user-guide.html#UserGuide-ManipulatingEndpoints
>
> If this is unclear I can try to create an actual process that does
> what I'm talking about.
>
> Thanks, Rich
>