Bruce,
That's what "retired" means. A process is retired so it can continue
executing existing instances, but not instantiate new ones. Undeploying is a
separate step that also removes all the instances.
Assaf
On 8/9/06, Bruce Snyder <[EMAIL PROTECTED]> wrote:
On 8/9/06, Assaf Arkin <[EMAIL PROTECTED]> wrote:
> My expectation as a developer, is that whenever I deploy a new version
of
> the same process, the old version is retired so the new version is
> activated. And if I intend to deploy two processes side by side, I
should
> pick different names to distinguish them.
>
> Anything else would surprise me.
What about a rolling deployment scenario? This might take place in a
production situation where P.v1 needs to remain active to service
client requests that are already open and running but P.v2 needs to be
used to service any new requests? I'm not sure that covering this case
using unique names is exactly the solution.
Bruce
--
perl -e 'print
unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://incubator.apache.org/activemq/
Apache ServiceMix - http://incubator.apache.org/servicemix/
Castor - http://castor.org/
--
CTO, Intalio
http://www.intalio.com
