3 Replies Latest reply on Jul 28, 2003 7:21 PM by Jon Barnett

    JBoss 3.2.1 ejb 1.1 compliance

    it_teky Newbie

      I am trying to migrate a perfectly working jar file (ejb 1.1 compliant) from jboss 2.4 to the latest version 3.2.1.

      I get the following warn/error message while deploying:

      17:20:38,811 WARN [verifier] EJB spec violation:
      Bean : MyDBBean
      Section: 16.2
      Warning: The Bean Provider must specify the fully-qualified name of the Java class that implements the enterprise bean's business methods.

      Does 3.2.1 work with ejb 1.1? or am I doing any wrong. Can anyone point me to any doc that talks about migration.

      I appreciate any ones help in figuring this.
      Regards
      ms

        • 1. Re: JBoss 3.2.1 ejb 1.1 compliance
          Jon Barnett Master

          It should work but you are probably encountering a problem with specifying the full class name, including the package in your ejb-jar.xml. JBoss 2.x didn't worry too much about this but you may find that this has been tightened somewhat and more compliant with the spec.
          e.g.
          com.amity.cards.CardsHome
          com.amity.cards.Cards
          <ejb-class>com.amity.cards.CardsBean</ejb-class>

          rather than:
          CardsHome
          Cards
          <ejb-class>CardsBean</ejb-class>

          Unless your classes don't specify a package. So just check your deployment descriptors. Most likely that is the issue.

          Hope it helps as I'm guessing. If it is not, post your deployment descriptors and I'm sure someone will have an answer.

          • 2. Re: JBoss 3.2.1 ejb 1.1 compliance
            it_teky Newbie

            jonlee,

            thanks for your reply.
            The actual problem is my startup class was accessing the beans before they got deployed. I need to make jboss invoke the startup class after all ejb's get deployed.

            nsm

            • 3. Re: JBoss 3.2.1 ejb 1.1 compliance
              Jon Barnett Master

              A surprising error message - did you solve the problem?