Temporary workaround to support controlling the lifecycle of the webserver runtime portion of TomcatDeployer via a JMX service in the deploy directory.
We want it in deploy so dependencies on services in deploy can be properly expressed. We want it as a JMX service so the ServiceBindingManager can
alter the connector ports.

Solution involves:

• Creating a wrapper mbean for the TomcatDeployer and deploying it via a deploy/jbossweb.sar/jboss-service.xml
• Encapsulating the code in TomcatDeployer that starts and stops the JBossWeb runtime in public start/stopWebserver methods.
• Disable calling those methods from TomcatDeployer.start/stop. Thus starting/stopping the deployer does not effect the runtime.
• Invoke the TomcatDeployer start/stopWebserver methods from the new wrapper mbean's startService/stopService.

A more long term solution involves:

• separating out the JBossWeb runtime aspects from TomcatDeployer and putting them in a separate class
• developing a ProfileService-based alternative to ServiceBindingManager so this doesn't need to be a JMX service