4 Replies Latest reply on May 23, 2003 2:45 AM by finn

    EJB spec violation (JBoss 3.2.0)

    finn
    finn May 20, 2003 6:51 AM

      Hi,

      I am trying to deploy a JAR file containing several beans but I get EJB spec violation on three of the beans, the rest works ok.

      EJB spec violation:
      Bean : Client
      Section: 22.2
      Warning: The Bean Provider must specify the fully-qualified name of the Java class that implements the enterprise bean's business methods in the <ejb-class> element.
      Info : Class not found: se.bl.wvsap.client.ClientEJB

      I have attached the server.log, ejb-jar.xml and the contentlist of the JAR file. The "missing" classes have the correct names,packages and locations as far as I can see. THe code works ok on Weblogic and this is the first time we are trying to get it to work on JBoss.

      I am new to JBoss and beans and I would appreciate any help/input.

      Thanks in advance,
      Lars

      • 2532 Views
      • Tags:
        • 1. Re: EJB spec violation (JBoss 3.2.0)
          adrian.brock May 20, 2003 10:04 AM (in response to finn)

          Start by putting the postgres driver in
          server/default/lib and reboot.

          Then we can see what is really going on.

          Regards,
          Adrian

            • Actions
          • 2. Re: EJB spec violation (JBoss 3.2.0)
            finn
            finn May 21, 2003 2:49 AM (in response to finn)

            Thanks for your quick reply Adrian,

            I put the postgresql JAR in the lib directory but I didn't notice any difference in the behaviour. I have attached the serverlog again in case you can spot any difference.

            By the way, I have tested a few simple entity bean examples and the link to the database seems to work ok.

            Regards,
            Lars

              • Actions
            • 3. Re: EJB spec violation (JBoss 3.2.0)
              adrian.brock May 21, 2003 1:43 PM (in response to finn)

              Postgres is deploying now,
              but jms isn't, you've removed hsqldb
              so the persistent manager isn't starting.

              For the ClassNotFoundException,
              it might be that the bean class uses a class
              you haven't deployed?

              The error reporting isn't very clear, it just checks
              whether it can load the class, it doesn't report
              the real error.

              You might be able to get more information by
              setting
              false
              for the EJBDeployer in server/default/conf/jboss-service.xml

              Regards,
              Adrian

                • Actions
              • 4. Re: EJB spec violation (JBoss 3.2.0)
                finn
                finn May 23, 2003 2:45 AM (in response to finn)

                Thanks ADrian,

                You were right. I was missing some other classes which the beans were dependent on. I am past the problems now :)

                /Lars

                  • Actions