10 Replies Latest reply on Nov 2, 2005 9:59 AM by bill.burke

    EJB 3 & JBoss4.0.3

    redijedi

      JBoss 4.0.3 does not seem to contain the ejb3 libs, is this true?

      I cannot seem to find any of the ejb3 libraries. JBossIDE, therefore, cannot find the libs for use in eclipse. Also, my ant script that used to work with 4.0.3RC1 cannot find import org.jboss.annotation.ejb.Management anymore. Is this a known issue, or have they been moved?

      I've downloaded the dist twice in case my dl was corrupt in some way. Still nothing.

      Observation:
      4.0.3 seems to be buggy. It's a shame it went to prod like this. Besides ejb prob listed above, webapps that worked on <= 4.0.2 no longer work.

        • 1. Re: EJB 3 & JBoss4.0.3
          neelixx

          Not sure what to tell you about the "buggy" comment. I'm working just fine on 4.0.3.

          As far as the EJB3.0, you'll need to install it using the graphical installer, and choose the EJB3.0 option.

          I believe this was the decision due to the fact that the EJB3.0 option is not a certified J2EE platform.........yet.

          • 2. Re: EJB 3 & JBoss4.0.3
            bill.burke

            also, EJB3 only works with Java 5 is another reason why it is not with the JBoss 4 zip. Also, EJB3 can be separately downloaded and installed into your JBoss installation. It currently works with JBoss 4.0.2 and greater. Another thing is that EJB3 is currently at release RC3 and the version that comes with the installer is RC2.

            As for your webapp problem. The classloading behavior was changed from 4.0.1->4.0.2 to match requirements in the specifications. Web classloaders are now scoped and isolated from rest of EAR.

            • 3. Re: EJB 3 & JBoss4.0.3
              tro1

              Working on a upgrade from AS 4.0.1 with EJB 3.0 preview 5, to AS 4.0.3 (used the installer).

              I'm not able to find @AssociationTable within the distribution, is it replaced by ... or not supported?

              This is my old prview 5 deployment description:

              @OneToMany(targetEntity = TextCMPBean.class, cascade = { CascadeType.PERSIST }, fetch = FetchType.LAZY)
              @AssociationTable(table = @Table(name = "TBL_TEXT_ORDER"), joinColumns = { @JoinColumn(name = "TAULENGDE_ID") }, inverseJoinColumns = { @JoinColumn(name = "ORDER_ID") })
              public Set getTexts() {...}



              • 4. Re: EJB 3 & JBoss4.0.3
                majohnst

                @AssociationTable has been renamed to @JoinTable. I ran into that problem myself.

                • 5. Re: EJB 3 & JBoss4.0.3
                  bill.burke

                  1) Don't use the installer. Use the EJB 3.0 RC3 distro. The installer has version RC2.

                  2) JoinTable has replaced AssociationTable.

                  • 6. Re: EJB 3 & JBoss4.0.3
                    redijedi

                    Thanks for all the replies. It seems to work better with the installer than with the add-on package.

                    The Management annotation also changed whihc through me off since the trailblazer on services does not note this.

                    • 7. Re: EJB 3 & JBoss4.0.3
                      henkomannen

                      Yes, regarding this @Management annotation change, is it documented somewhere? Would like some info about it.

                      • 8. Re: EJB 3 & JBoss4.0.3
                        kabirkhan

                        I believe it now has been moved from the interface to the bean class. Try

                        @Service
                        @Management (MyManagementIF.class)
                        public class MyBean implements MyManagementIF
                        {

                        }

                        It should eventually be useable on both the interface and on the bean class, as with @Remote/@Local

                        • 9. Re: EJB 3 & JBoss4.0.3
                          henkomannen

                           

                          "kabir.khan@jboss.com" wrote:

                          @Service
                          @Management (MyManagementIF.class)
                          public class MyBean implements MyManagementIF
                          {

                          }


                          Yupp, correct. It works for me now. I tried this strategy but without compiling my project in eclipse with the JBoss 4.0.3SP1 specific lib's included, but those for JBoss 4.0.3RC2. DOH! Then I got an exception at deploy time, but that's gone now.

                          Thanks for the confirmation.

                          • 10. Re: EJB 3 & JBoss4.0.3
                            bill.burke

                            who changed this? It was supposed to be able to be used on both.