Ok, so my current tactic is to create a TomcatService class which would take over the code from TomcatDeployer which starts and stops Tomcat, to be placed in deploy. That's relatively easy. What's much harder to me is how to handle TomcatDeployment, which has lots of dependencies and extends AbstractWarDeployment. The class takes care of the actual deployment, and would thus need to be split in two. The "active" parts which depend on Tomcat (the preform(Un)Deploy methods) would be moved to the TomcatService class, and called using JMX. I suppose this would work, but involves passing around a lot of objects. I would still appreciate some concrete help with this stuff :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125538#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...