anonymous wrote : What's much harder to me is how to handle TomcatDeployment, which has lots of dependencies and extends AbstractWarDeployment. My understanding is that AbstractWar/TomcatDeployment are encapuslated by the WebModule MBean that is used to "populate" the runtime. It is the WebModule that is created as the ServiceMetaData description by the deployers and it delegates to the Deployment which in turn "talks to" the runtime in the start/stop once dependencies are resolved (e.g. the clustering implementation or ejb-links resolved) This could probably be simplified (a lot :-) At least since WebModule seems to be doing little except possibly avoiding a change in api at some previous point in history? The link to AbstractWarDeployer (described as "container") in the WebModule should probably be changed to be the runtime service? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125582#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...