5 Replies Latest reply on Sep 10, 2002 9:12 AM by Juha Lindfors

    Using JbossMX in standalone application

    Alexander Kogan Newbie

      Hello,

      I'm going to use JbossMX as a "backbone" for our new
      pilot project. I suspect I don't have to, but I'd better ask for a permission to do that.

      The project is about a fullblown java application
      (with native graphics, native geometry engine, a lot
      of UI, peer2peer comm. and etc.).
      This application also will be a client for several customized application servers (built on Jboss).

      If you, guys, have nothing against it, I'd like to
      ask a couple of questions:

      - is JbossMX ready for such task? Or it is better to
      stuck to Sun RI for a while and switch to JbossMX
      later.

      - will JbossMX be developed in accordance with JSR-160
      (I think so, but just want to be sure).

      Thanks in advance.
      Alex.

        • 1. Re: Using JbossMX in standalone application
          Nathan W. Phelps Novice

          Along the same lines as this, I'd really love to see all the JBossMX, the MBean Services framework, the logging MBean, and the SAR deplorer broken out into a separate package. You guys did JSR 111 before JRS 111 even existed! I've looked in to Apache Phoenix, but what you guys have is better. I'd love be able to use this framework for stand alone server applications. I realize that is completely possible right now, but you have to do a bit of work to eliminate all the JBoss J2EE specific code (like the EJB Service, the JMS service, etc.) What I'm getting at is a formalization of the road you guys are already going down.

          • 2. Re: Using JbossMX in standalone application
            Juha Lindfors Master

            > I'm going to use JbossMX as a "backbone" for our new
            > pilot project. I suspect I don't have to, but I'd
            > better ask for a permission to do that.

            Feel free. It's LGPL.

            > The project is about a fullblown java application
            > (with native graphics, native geometry engine, a lot
            > of UI, peer2peer comm. and etc.).
            > This application also will be a client for several
            > customized application servers (built on Jboss).
            >
            > If you, guys, have nothing against it, I'd like to
            > ask a couple of questions:
            >
            > - is JbossMX ready for such task? Or it is better to
            > stuck to Sun RI for a while and switch to JbossMX
            > later.

            JBossMX hasn't been released yet, so if you're planning to start today, RI might be the way to go. We'll make an alpha release of JBossMX this month, and will try to move to beta and 1.0 release as soon as possible.

            > - will JbossMX be developed in accordance with
            > JSR-160 (I think so, but just want to be sure).

            yes, as soon as it becomes public.

            -- Juha

            • 3. Re: Using JbossMX in standalone application
              Juha Lindfors Master

              > Along the same lines as this, I'd really love to see
              > all the JBossMX, the MBean Services framework, the
              > logging MBean, and the SAR deplorer broken out into a
              > separate package. You guys did JSR 111 before JRS
              > 111 even existed! I've looked in to Apache Phoenix,
              > but what you guys have is better. I'd love be able
              > to use this framework for stand alone server
              > applications. I realize that is completely possible
              > right now, but you have to do a bit of work to
              > eliminate all the JBoss J2EE specific code (like the
              > EJB Service, the JMS service, etc.) What I'm getting
              > at is a formalization of the road you guys are
              > already going down.

              I agree with you. That's one of the goals of JBossMX to generalize the features that you can find in JBoss today as a generic service framework that addresses logging, security, deployment and so on.

              That being said, alot of this can already be achieved with the current (2.4.4) codebase, and the upcoming 3.0 release should make it even easier. Both 2.x and 3.x releases are based on JMX and most services can be disabled/enabled quite easily through the configuration files.



              • 4. Re: Using JbossMX in standalone application
                ming luo Newbie

                If I use JBossMX in a standalone process, how can I initialize the adaptors(e.g. Html adaptor and RMI connector)? i mean I don't know which class to call. In SUN RI, their under com.sun.jdmk.comm package. Where is the corresponding adaptors/connectors in JbossMX? Which package, and jar file?

                thanks
                ming

                • 5. Re: Using JbossMX in standalone application
                  Juha Lindfors Master

                  You can download the source code for the JMX book (see the documentation page). It contains classes for rmi and soap connectors. These should work without additional j2ee services (such as jndi) as far as I remember.

                  For the JMS connector you need to run MQ standalone at least (naming services too). For the JBoss rmi connector you probably need jndi too at least. And for the JBoss html adaptor you will need a servlet container at minimum.