"scott.stark(a)jboss.org" wrote : First, I'm not in agreement that hot deployment of deployers is needed. The only post bootstrap configuration I can see are aspects on the deployers themselves, but this can be a function of an individual deployment, not neccessarily a reconfiguration of the deployer. | | Second, explain how the tree is used given a DeploymentContext representing an ear with the full contigent of javaee components, and customized aspects like security and logging. | I don't think it is important to support the redeploy and undeployment of a deployer, but generalize deployment does seem important. I like my original idea of the .deployer archive and packaging subsystems like EJB3 and AOP in deployer archives. Makes it easy for people to add/remove/patch these subsystems. Maybe the JEMS installer makes this point moot, but I think we should retain some traditions here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973081#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...