2 Replies Latest reply on Jun 29, 2010 10:54 AM by Olaf Bergner Branched to a new discussion.

    Is JBoss 6 already up to this task?

    Olaf Bergner Newbie

      I'm currently implementing a prototype application meant to evaluate the usefulness of JEE6 in general and CDI specifically for my needs. Since mine is not a web application but rather a complex back office solution divided into several modules using contract-first web services and JMS as its remoting layer, an appropriate application server should fulfill the following requirements:

       

      1. Ear deployment
      2. Possibility to keep JPA entities in separate jars which may be referenced by multiple ejb-jars
      3. CDI support
      4. Mature web service stack
      5. JMS support

       

      Since Glassfish is currently the only certified JEE6-compliant application server I thus far based my prototype on Glassfish 3.0.1. Lately though, I ran into a major bug in Glassfish that surfaces whenever an ejb-jar references a persistence unit which resides in another jar (see 2. above). The net effect is that CDI is effectively unusable in that situation. Since CDI is to me the most important part in the JEE 6 specification this makes Glassfish in its current shape a no-go.

       

      As I said this is only a prototype meant to assess the viability of certain technologies in the face of my specific requirements. I would therefore be willing to switch to JBoss 6 although it still seems a far cry from being stable. Furthermore, I don't my tracking snapshot builds. On the other hand I don't want to waste my time attempting something that is currently still doomed to fail.

       

      So what I would like to know is whether JBoss 6 in its current shape is up to the task described above, or else if there are still so many gaps in its current implementation that I should rather refrain from trying.

       

      Thx,

      Olaf

        • 1. Re: Is JBoss 6 already up to this task?
          jaikiran pai Master

          Olaf,

           

          Welcome to the forums.

           

          Olaf Bergner wrote:

           

          I'm currently implementing a prototype application meant to evaluate the usefulness of JEE6 in general and CDI specifically for my needs. Since mine is not a web application but rather a complex back office solution divided into several modules using contract-first web services and JMS as its remoting layer, an appropriate application server should fulfill the following requirements:

           

          1. Ear deployment

          Definitely, (any version of) JBoss AS allows this (and so do other application servers).

           

          Olaf Bergner wrote:

           

          2. Possibility to keep JPA entities in separate jars which may be referenced by multiple ejb-jars

          The rules for this are governed by the JPA spec and aren't specific to JBoss AS.

           

          Olaf Bergner wrote:

           

          3. CDI support

          Yes, the latest 6.0.0 M3 of JBoss AS provides this.

           

          Olaf Bergner wrote:

           

          4. Mature web service stack

           

          Yes, JBoss AS has this.

           

          Olaf Bergner wrote:

           

          5. JMS support

             

            Yes, JBoss AS has this. Infact, the latest version 6.0.0 M3 of JBoss AS has the impressive HornetQ by default.

             

            You might also want to go through these series of articles/tutorials before deciding what you require http://in.relation.to/Bloggers/AHitchhikersGuideToJavaEE6ApplicationSetupPartI

            • 2. Re: Is JBoss 6 already up to this task?
              Olaf Bergner Newbie

              Hi Jaikiran,

              thanks for your efforts, I will definitely give JBoss a try.

               

              {quote}

               

              Olaf Bergner wrote:

               

              I'm currently implementing a prototype application meant to evaluate the usefulness of JEE6 in general and CDI specifically for my needs. Since mine is not a web application but rather a complex back office solution divided into several modules using contract-first web services and JMS as its remoting layer, an appropriate application server should fulfill the following requirements:

               

              1. Ear deployment

              Definitely, (any version of) JBoss AS allows this (and so do other application servers).

              {quote}

               

              I asked this question because I got a strange exception as soon as I added a jboss-app.xml deployment

              descriptor to my ear. Therefore, I suspected that JBoss 6 may not support ear deployment yet.

               

              {quote}

              Olaf Bergner wrote:

               

              2. Possibility to keep JPA entities in separate jars which may be referenced by multiple ejb-jars

              The rules for this are governed by the JPA spec and aren't specific to JBoss AS.

              {quote}

               

              Yes, I thought so, too, but Glassfish seems to have a lot of problems with this setup.

               

              {quote}

              Olaf Bergner wrote:

               

              4. Mature web service stack

              Yes, JBoss AS has this.

              {quote}

              Since my web services were originally developed on Glassfish's Metro stack, and since JBossWS is rumored

              to support Metro, I would naturally like to use this option. Does anyone know what I have to do to

              activate Metro support in JBoss 6? I'm asking since deploying my unmodified web services on top of JBoss 6'

              default CXF stack fails. Metro and CXF - amongst other differences - seem to resolve the "wsdlLocation"

              attribute differently.

               

              Many thanks,

              Olaf