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.
Cheers, Rich On Nov 13, 2007 8:19 AM, Matthieu Riou <[EMAIL PROTECTED]> wrote: > On Nov 12, 2007 4:07 PM, RichTaylor <[EMAIL PROTECTED]> 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. > > > > >
