Details
-
Feature Request
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
Description
This issue is to track the need/ways to implement JSR77 support in JBoss Messaging.
There is no requirement in TCK for JSR77.
Details in the attached forum thread.
Changing JMSService attribute for the management Mbean from jboss.mq:service=DestinationManager to jboss.messaging:service=ServerPeer creates a JMSResource for JBoss Messaging.
More details on this from the email discussions.
It's not clear how much of jsr77 we implement when it comes to JMS/JBossMQ
The piece that sets up the jsr77 domain in conf/jboss-service.xml:
...
<!-- ==================================================================== -->
<!-- JSR-77 Single JBoss Server Management Domain -->
<!-- ==================================================================== -->
<mbean code="org.jboss.management.j2ee.LocalJBossServerDomain"
name="jboss.management.local:j2eeType=J2EEDomain,name=Manager">
...
<attribute name="JMSService">jboss.mq:service=DestinationManager</attribute>
...
By simply providing a valid mbean in place of the MQ destination manager, might make org.jboss.test.management.test.JSR77SpecUnitTestCase.testJMSResource to pass, since this will create the "LocalJMS" RMSResource.
I don't see org.jboss.mq.server.jmx.DestinationManager generating any special notification to feed the jsr77 subsystem, nor MQ importing any javax.management.j2ee or org.jboss.management classes.
