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

[adrian@jboss.org]

"bstansberry at jboss.com" wrote : 
  | 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.

As long the components are written to respond to the activate() callback
and not the start() callback.
i.e. the container is created but its frontend isn't bound into jndi
or linked as a valid web context etc.

That's certainly a better semantic for the valve/redeploy processing since it almost
becomes an atomic swap/failover instead of waiting for the full undeploy/deploy
cycle. But there's many other issues to resolve before we can get there,
e.g. not using the default "big ball of mud" classloading configuration :-)

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

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