[jboss-jira] [JBoss JIRA] Updated: (JBAS-5966) Migrate TomcatService mbean deployment descriptor to mc bean descriptor

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated JBAS-5966:
-----------------------------------

    JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=139777


To clarify a bit on the need for this:

The ModClusterService integration works by adding a special LifecycleListener to server.xml that does an MC lookup of the ModClusterService pojo. See forum thread.  The class that does the MC lookup has a ref to the KernelController injected into it by TomcatService.  But that doesn't work if TomcatService isn't deployed via a -jboss-beans.xml -- the MC doesn't inject the KernelControllerContext into TomcatService.setKernelControllerContext(...) if the service is deployed as an mbean.

There might be other ways of doing this integration; e.g. adding an mbean attribute to TomcatService and injecting the controller. But this seems like a service that should be deployed via a -beans.xml anyway.

> Migrate TomcatService mbean deployment descriptor to mc bean descriptor
> -----------------------------------------------------------------------
>
>                 Key: JBAS-5966
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5966
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service
>    Affects Versions: JBossAS-5.0.0.CR1
>            Reporter: Paul Ferraro
>            Assignee: Remy Maucherat
>             Fix For: JBossAS-5.0.0.GA
>
>
> The deployment descriptor for org.jboss.web.tomcat.service.deployers.TomcatService uses the legacy mbean descriptor.
> This prevents the user from adding a dependency on a microcontainer bean (e.g. for mod_cluster integration).
> The current descriptor, expressed as a jboss-beans.xml file would look like this:
> <?xml version="1.0" encoding="UTF-8"?>
> <deployment xmlns="urn:jboss:bean-deployer:2.0">
>    <bean name="WebServer" class="org.jboss.web.tomcat.service.deployers.TomcatService">
>          
>       <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.web:service=WebServer", exposedInterface=org.jboss.web.tomcat.service.deployers.TomcatServiceMBean.class,registerDirectly=true)</annotation>
>       <!-- Only needed if the org.jboss.web.tomcat.service.jca.CachedConnectionValve
>            is enabled in the tomcat server.xml file.
>       -->
>       <depends>jboss.jca:service=CachedConnectionManager</depends>
>       <!-- Transaction manager for unfinished transaction checking in the CachedConnectionValve -->      
>       <depends>jboss:service=TransactionManager</depends>
>       
>       <!-- Inject the TomcatDeployer -->
>       <property name="tomcatDeployer"><inject bean="WarDeployer"/></property> 
>     
>       <!-- 
>          Do not configure other JMX attributes via this file.
>          Use the WarDeployer bean in deployers/jboss-web.deployer/war-deployers-beans.xml
>       -->
>    </bean>
> </deployment>

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