[jboss-dev-forums] [Design of POJO Server] - Re: Controlling deployments via a barrier bean

[adrian@jboss.org]

"bstansberry at jboss.com" wrote : 
  | Essentially we're talking about another step in the lifecycle -- create/start/activate/deactivate/stop/destroy that all containers would have to support.
  | 

I don't really see it as a true lifecycle step since you're NOT waiting to resolve a
dependency. The context is in a valid final state, its just inactive.

I suppose you could see it as an alternative to the "Installed" state, e..g
InstalledInactive and InstalledActive could be alternate states
with some processing going on when it switches between the states.

But the transistion is decided by some arbitrary notiifcation, not a dependency
(unless you count the dependency on oneself being installed :-)

anonymous wrote : 
  | Thinking a bit about whether that maps to the "valve" concept where (AIUI) a component is brought all the way to DeploymentStage.REAL and in a final change to  DeploymentStage.INSTALLED external things like JNDI refs, request pipelines etc are switched.
  | 

It certainly relates to the valve, but the valve mainly involves tracking and waiting
for requests to complete. 
Again this could be considered a different state
where you allow old requests but hold/deny new ones.
A sort of "InstalledDeactivating"  state. ;-)

Whether we would actually implement it that way, is a different issue.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155770#4155770

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155770