On Wed, May 7, 2008 at 11:45 AM, Tammo van Lessen <[EMAIL PROTECTED]> wrote:
> Agreed. It seems both of these states should be part of the persistent > > state of the process definition in the ProcessStore, but not necessarily > > exposed in the deployment descriptor. Is that what you meant? > > > > That's particularly what I meant :) These states definitely make sense > after the deployment but I was missing a scenario where I want to initially > deploy a retired model. The active state makes sense if I want to deploy a > bunch of process models that I want to selectively activate later using the > PMAPI (more in terms of activating the service endpoint, as the number of > process models is actually not an issue). For historical perspective, deploy.xml was designed before we introduced the ProcessStore so having these states in the deployment descriptor made sense at the time (well, sort of). It's one of these things where we didn't go back and clean up (or explicitly deprecate) when the design changed. So I agree we should clean it up on the trunk. alex
