I think that clarifies it, and also suggests that our terminology is not
the best. The things that is confusing is that the retired processes are
not "inactive". Lance's 'current' is better in this respect, but has no
good opposite (perhaps "legacy").
-mbs
On Tue, 2006-08-08 at 14:11 -0700, Alex Boisvert wrote:
> Ok, so maybe the wording was confusing so I'll give a concrete example
> or two to clarify.
>
> Say I deploy process P (v1) with initiating operation "foo" on endpoint
> "bar"
>
> I cannot redeploy a new version of P with the same operation and same
> endpoint unless P (v1) has been retired or undeployed.
>
> If I retire P (v1) and deploy a new P (v2) with the same operation and
> endpoint, then I cannot reactivate P (v1) unless P (v2) has been retired
> or undeployed.
>
> alex
>
>
> Maciej Szefler wrote:
> > Alex,
> > I don't think the following makes sense:
> >
> > On Tue, 2006-08-08 at 11:26 -0700, Alex Boisvert wrote:
> >
> >> New process definitions may "override" the initiating operations and
> >> endpoints of retired process definitions to provide transparent
> >> migration to existing service consumers. To prevent conflicts,
> >> deploying a process definition using the same initiating operation(s)
> >> and the same endpoint(s) of an already deployed process should fail.
> >> Similarly, retired processes could be re-activated if no process
> >> currently uses the same initiating operation(s) on the same endpoints.
> >>
> >
> > A new process version, should--in fact I think it must--have the same
> > initiating operations and endpoints. The new version of the process is
> > deployed in the server on exactly the same endpoints as the old. The
> > server manages the routing to make sure that the correct version of the
> > process receives the correct messages. This can be done fairly easily
> > and allows the "client" of the process to be completely oblivious to the
> > fact that a new version has been deployed: the client keeps sending
> > messages to the same BPEL engine endpoint.
> > -mbs
> >
> >
> >
>
