2 Replies Latest reply on Feb 27, 2008 6:54 AM by Andy Taylor

    JBM 2.0 Standalone

    Andy Taylor Master

      How do we want to ship a standalone JBM 2 deployment.

      If we want to use the MC as the bootstrap, as the current JBMBootstrapServer server class does, the makes the MC a dependancy. Alternatively we could just write our own , Server.main(), but this wouldn't be pluggable.

      Also If its a full JMS Server then the user needs a naming server running, do we ship the JBOSS one as a default? i.e. jnpserver.jar.

      do we ship using the NullAuthenticationManager, would this be enough for users?

        • 1. Re: JBM 2.0 Standalone
          Tim Fox Master

           

          "ataylor" wrote:
          How do we want to ship a standalone JBM 2 deployment.


          We have three usage modes, probably worth looking at my JBM 2.0 slides - it goes into this in depth.

          1) In JBoss AS (in MC)
          2) "Standalone" - this is just in the MC too - but without all the other AS services, but with "useful" services like JNDI and the JMSServerManager as well as the core.
          3) Embedded - this is just the core class directly instantiated in a user application (OEM). Core has no JNDI, JMS, MC dependencies.


          If we want to use the MC as the bootstrap, as the current JBMBootstrapServer server class does, the makes the MC a dependancy.


          It's not a dependency from core though - the boostrap class should live outside core.


          Alternatively we could just write our own , Server.main(), but this wouldn't be pluggable.


          That's up to the user to do if they like.


          Also If its a full JMS Server then the user needs a naming server running, do we ship the JBOSS one as a default? i.e. jnpserver.jar.


          See previous comments.


          • 2. Re: JBM 2.0 Standalone
            Andy Taylor Master

            Ok, the current standalone remote configuration starts the jboss naming server(see remote.xml, I'll tidy this up a bit.