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

[bstansberry@jboss.com]

Re: the property replacement, yeah, my question wasn't clear. I'll open another thread.

"adrian at jboss.org" wrote : That's why I suggested a jboss-activation.xml to try to make it easier to manage. The downside is it pushes the responsibility of this new metadata to the subsystems to read it, since only they know what it means to activate their fine-grained component.

Essentially we're talking about another step in the lifecycle -- create/start/activate/deactivate/stop/destroy that all containers would have to support.

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.

Interesting thing to me about this is for JEE components it allows a fast activation following ha singleton failover, since the service is 90+% ready to go when the node becomes master.

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

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