"jhalliday" wrote : From the sounds of things it would be feasible to declare a
bean with
class=org.jboss.system.microcontainer.jmx.ServiceControllerLifecycleCallback in
the jboss-service.xml file and inject the legacy JMX kernel into it, then
reference that in the TransactionManager bean xml?
Exactly.
This is what solves your problem:
| <bean name="MBeanExporter"
class="org.jboss.system.microcontainer.jmx.ServiceControllerLifecycleCallback">
| <property name="serviceController"><inject bean="JMXKernel"
property="serviceController"/></property>
| </bean>
|
| <bean name="TransactionManager"
class="org.jboss.tm.RealTransactionManager">
|
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=TransactionManager",
exposedInterface=org.jboss.test.system.controller.integration.support.MockTransactionManagerMBean.class,
registerDirectly=true)</annotation>
| <property name="transactionTimeout">300</property>
| <property
name="objectStoreDir">${jboss.server.data.dir}/tx-object-store</property>
| <install bean="MBeanExporter" method="install">
| <parameter><inject fromContext="context"/></parameter>
| </install>
| <uninstall bean="MBeanExporter" method="uninstall">
| <parameter><inject fromContext="context"/></parameter>
| </uninstall>
| </bean>
|
And since the AOP kicks in later, this bean won't be picked up twice for JMX
registry - conclusion from Adrian's comment.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116533#4116533
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116533
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
