2 Replies Latest reply on Jan 7, 2002 1:47 AM by Brian Huang

    JBoss-3.0.0alpha vs JBoss-2.4.4

    Brian Huang Newbie

      JBoss-2.4.4 was just released. Is JBoss-3.0.0 under development?

      I try to deploy EJBs using EJB2.0 to JBoss-2.4.4, the following warnings will be shown:

      The entity bean must not be defined as abstract.

      The entity bean must define a public constructor that takes no arguments.

      The primkey-field element must name a public field in the bean implementation class.

      However, it worked under JBoss3.0.0alpha. In addition, if I use MVCSoft Persistence Manager to regenerate an EJB jar, I can deployed it to JBoss2.4.4.

      Is it safe to develop a project using JBoss3.0.0 if I don't use JSP or what should I avoid?

      Brian




        • 1. Re: JBoss-3.0.0alpha vs JBoss-2.4.4
          Dain Sundstrom Master

          > JBoss-2.4.4 was just released. Is JBoss-3.0.0 under
          > development?

          Yes

          > I try to deploy EJBs using EJB2.0 to JBoss-2.4.4, the
          > following warnings will be shown:
          >
          > The entity bean must not be defined as abstract.
          >
          > The entity bean must define a public constructor that
          > takes no arguments.
          >
          > The primkey-field element must name a public field in
          > the bean implementation class.

          This is because CMP 2.0 is a JBoss 3.0 only feature.

          > However, it worked under JBoss3.0.0alpha.

          Because CMP 2.0 works in JBoss 3.0.

          > In addition, if I use MVCSoft Persistence Manager to
          > regenerate an EJB jar, I can deployed it to
          > JBoss2.4.4.

          Because, MVCSoft generates EJB 1.1 BMP entities from your CMP 2.0 code.

          > Is it safe to develop a project using JBoss3.0.0 if I
          > don't use JSP or what should I avoid?

          Yes, if you don't want to go into production right away (although Hunter is using 3.0 in production). You can use JSPs in 3.0, but you will need the cvs source.

          I would suggest building from source every week or so.

          • 2. Re: JBoss-3.0.0alpha vs JBoss-2.4.4
            Brian Huang Newbie


            Regarding the warnings as followed,
            > The entity bean must not be defined as abstract.
            >
            > The entity bean must define a public constructor that
            > takes no arguments.
            >
            > The primkey-field element must name a public field in
            > the bean implementation class.
            I found the cause of them. It was because the missing of <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/j2ee/dtds/ejb-jar_2_0.dtd"> tag.

            I commented it out for editing my ejb-jar.xml file offline. When I uncomment it, the warnings are gone and things are ok.

            Thanks.

            I need programmers to code under jboss 3.0.0. Any suggestions?

            Brian