ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Taylor" <bhamtay...@gmail.com>
Subject Re: Change endpoint after deployment?
Date Tue, 13 Nov 2007 22:02:49 GMT
Just re-read this, should have started the second paragraph with
"However, in the case I'm interested in..."    - Rich

On Nov 13, 2007 2:00 PM, Rich Taylor <bhamtaylor@gmail.com> wrote:
> As for the registry I was referring to the BPEL process actually
> invoking a getEndpointForService SOAP call on an external registry
> (i.e. UDDI).  That call would return an endpoint reference which could
> then be set on a partnerlink.  That would be the more dynamic approach
> that may apply in some cases
>
> When the endpoint URLs are specified in deploy.xml, they are processed
> at deployment and put into the DB.  So you're saying that if I were to
> change the endpoint URL on a process definition in the database it
> would be used for future instances of that process.   I was thinking
> that the deploy.xml might need to be changed as well, for restarts,
> but it doesn't sound like that's the case.  It would just need to be
> changed in deploy.xml for future deployments.
>
> And you're saying that this change to the endpoint URL in the DB could
> be done via the Mgt API, with/after some modifications.   Gotcha
>
> Thanks, Rich
>
> p.s. I just replied to your other emails, had missed them.
>
>
> On Nov 13, 2007 1:09 PM, Matthieu Riou <matthieu@offthelip.org> wrote:
> > On Nov 13, 2007 11:39 AM, Rich Taylor <bhamtaylor@gmail.com> wrote:
> >
> > > I was thinking programmatically via the Management API, not so much
> > > from the BPEL itself.   Sounds like it's not in there now but isn't
> > > too far fetched of an idea to implement.  The use case I had
> > > envisioned is in a deployment where someone has one or more processes
> > > pointing to a service, and the service changes its published port or
> > > endpoint URL in some other way, they would have to reploy all of their
> > > processes.   It sounds like if that is a concern then the BPEL should
> > > obtain endpoint values from some sort of registry before invoking
> > > them. Please correct me if I'm wrong on this last part, and either
> > > way, thanks for the reply.
> > >
> >
> > Nothing wrong, it's a completely valid use case. Actually I thought I had
> > implemented methods in the management API to do this before but I've either
> > been dreaming or it got lost at some point. For these endpoints there's no
> > real need of a registry as we have values on a per process and per instance
> > basis, the value for an instance overrides the one on a process.
> >
> > So if you simply change the endpoint on a process definition in the database
> > it should do what you're looking for I think.
> >
> > Cheers,
> > Matthieu
> >
> > P.S. I've sent you a few e-mails directly, did you get them?
> >
> >
> >
> > >
> > > Cheers, Rich
> > >
> > > On Nov 13, 2007 8:19 AM, Matthieu Riou <matthieu@offthelip.org> wrote:
> > > > On Nov 12, 2007 4:07 PM, RichTaylor <bhamtaylor@gmail.com> wrote:
> > > >
> > > > >
> > > > > Is it possible to change an endpoint reference after a process has
> > > been
> > > > > deployed?  For example if your process invokes a service at
> > > http://foo/a,
> > > > > is
> > > > > it possible to change the process to cal http://foo/b for future
> > > > > executions,
> > > > > without redploying the process?
> > > > >
> > > >
> > > > Do you want to do that programmatically? Or in your BPEL? If the latter
> > > you
> > > > can use partner link assignment and directly set a URL. If the former
> > > > there's nothing right now on the public API but if the BPEL solution
> > > doesn't
> > > > work for you it wouldn't be too complicated to add. You would need to
> > > add
> > > > that to the ProcessInstanceManagement interface and look up the scope
> > > that
> > > > would give you the partner link where endpoints are stored.
> > > >
> > > > Cheers,
> > > > Matthieu
> > > >
> > > >
> > > >
> > > > >
> > > > > I get the impression you could do this by using a dynamic endpoint
and
> > > > > retrieving the URL from a factory of some sorts.  But what about
> > > endpoints
> > > > > that were specified/hard coded in depoy.xml?
> > > > >
> > > > > I see ProcessManagement.setProcessProperty() but I'm not sure that
is
> > > even
> > > > > related.
> > > > >
> > > > > Thanks! Rich
> > > > > --
> > > > > View this message in context:
> > > > >
> > > http://www.nabble.com/Change-endpoint-after-deployment--tf4793826.html#a13714152
> > > > > Sent from the Apache Ode User mailing list archive at Nabble.com.
> > > > >
> > > > >
> > > >
> > >
> >
>

Mime
View raw message