[jboss-jira] [JBoss JIRA] Created: (JBAS-5191) Manage JBoss Web runtime lifecycle via a JMX service in deploy

[Brian Stansberry (JIRA)]

Manage JBoss Web runtime lifecycle via a JMX service in deploy
--------------------------------------------------------------

                 Key: JBAS-5191
                 URL: http://jira.jboss.com/jira/browse/JBAS-5191
             Project: JBoss Application Server
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Web (Tomcat) service
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: JBossAS-5.0.0.Beta4


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



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira