I think this has to do with JBI, where you delegate lifecycle management to the container by exposing an API it can use to start/stop/shutdown individual service units.
Assaf On 8/17/06, Lance Waterman <[EMAIL PROTECTED]> wrote:
From the IL/client's perspective, it seems like control over when a process is "suspended" is the correct level of management. Whether a process is loaded into memory or not seems like an engine detail that the IL/client shouldn't really care about - but perhaps I'm missing a nuance in this. Lance On 8/17/06, Maciej Szefler <[EMAIL PROTECTED]> wrote: > > you missed one: > a process can be deployed, but "suspended": this allows you to prevent > work being performed on behalf of any of the process instances without > undeploying it. > > -mbs > On Thu, 2006-08-17 at 12:16 -0700, Assaf Arkin wrote: > > also confused by terminology here. > > > > Specific process instance can be in memory doing some work, or in the > > database. > > Specific process instance can be suspended (not processing events even > > if they arrived)/resumed. > > Process definition can be deployed or not. > > Deployed process definition can be used to instantiate new processes > > or not. > > > > What would be the best way to name those? > > > > Assaf > >
-- CTO, Intalio http://www.intalio.com
