This content has been marked as final.
Show 4 replies
-
1. Re: Topics/Queues as MC Beans
anil.saldhana Nov 24, 2008 5:23 PM (in response to anil.saldhana)I think I have the mbean name wrong. There probably lies the issue. :(
-
2. Re: Topics/Queues as MC Beans
adrian.brock Nov 24, 2008 5:35 PM (in response to anil.saldhana)"anil.saldhana@jboss.com" wrote:
I think I have the mbean name wrong. There probably lies the issue. :(
Nope. Try this:<?xml version="1.0" encoding="UTF-8"?> <deployment xmlns="urn:jboss:bean-deployer:2.0"> <bean name="QueueEJB3MDB" class="org.jboss.mq.server.jmx.Queue"> <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.messaging.destination:service=Queue,name=QueueEJB3MDB", exposedInterface=org.jboss.mq.server.jmx.QueueMBean.class, registerDirectly=true)</annotation> <property name="JNDIName">QueueEJB3MDB</property> <property name="serverPeer">jboss.messaging:service=ServerPeer</property> <depends>jboss.messaging:service=PostOffice</depends> </bean> </deployment>
which creates the POJO but makes sure it also gets registered with JMX
so not much different from the mbean really.
AFAIK the version of jboss messaging in jboss5 hasn't been "pojoized"
but there is a later version that has. -
3. Re: Topics/Queues as MC Beans
adrian.brock Nov 24, 2008 5:38 PM (in response to anil.saldhana)The version of the wrapper you are using is meant as a backwards compatiblity thing
for people that have old jbossmq configurations but want to use jboss messaging
without having to redo their destination configurations.
If you're doing it from scratch, you should use the QueueService directly. -
4. Re: Topics/Queues as MC Beans
anil.saldhana Nov 24, 2008 5:54 PM (in response to anil.saldhana)Thanks Adrian. I figured out that I was missing a JMX annotation and was trying to figure out how to convert the exposedInterface as a class instance from the xml file. :) Thanks for the example and I learned it.
I will directly use QueueService.