1 Reply Latest reply on Nov 30, 2009 11:24 AM by menegazzo

    Question about queues / topics and MBeans

    tashtego

      Hi.

      I am a bit new to message driven beans. Trying my first steps right now. I´ve already read the following articles:

      http://activemq.apache.org/version-5-hello-world.html

      http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/tmj_devcl.html

      http://www.roseindia.net/ejb/example-of-messageBean.shtml

      Now my wish would be to create a queue or topic within my application instead of having to create xml files which have to be placed into deploy folder as -service.xml files. Is this possible? How?

      The JBoss Admin-Console tells me this:
      Created Programmatically: false

      So it should be possible I guess. And what do MBeans have to do with this? I never programmed a MBean so far. What are those custom programmed MBeans good for? I know many services of JBoss run as modules (MBeans?). Is creating a queue another possible example for this?

      thanks for any comments about this!

        • 1. Re: Question about queues / topics and MBeans
          menegazzo

          Hello, please check this:
          http://docs.jboss.org/jbossas/getting_started/v4/html/mdb.html

          Other useful links:
          Do you need an assynchronous message system?
          http://jboss.org/hornetq
          Or a simple solution like a scheduler?
          http://www.quartz-scheduler.org/docs/index.html



          And what do MBeans have to do with this?

          From the 1st link above:

          As with most things in JBoss, JMS Topics and Queues are implemented using MBeans. There are two ways you can create them: you can add MBean declarations to the appropriate configuration file, or you can create them dynamically using the JMX Console. However, if you use the latter method, they wont survive a server restart.



          What are those custom programmed MBeans good for?

          I'm new to all this stuff too, but i think JMX MBeans were designed to provide interfaces for management through administration consoles and other stuff.


          The JMX technology provides the tools for building distributed, Web-based, modular and dynamic solutions for managing and monitoring devices, applications, and service-driven networks. By design, this standard is suitable for adapting legacy systems, implementing new management and monitoring solutions, and plugging into those of the future.
          http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/


          hope it helps