3 Replies Latest reply on Aug 29, 2005 7:16 PM by Paul Wallace

    EJB deployment problem

    Paul Wallace Newbie

      Hi,
      I am new to JBoss/EJB, and have built my stateless session bean via my IDE so I think the syntax of all three (home, remote and bean) classes are fine and they compile. My ejb-jar.xml is in META-INF under my src root (below).
      I run Ant to bundle them all up in to the deploy (default) dir of JBoss. The JAR is there with * 3 classes plus ejb-jar.xml and manifest. The console shows:

      09:06:06,294 WARN [verifier] EJB spec violation:
      Bean : TestSessionEJB
      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.

      09:06:06,294 WARN [verifier] EJB spec violation:
      Bean : TestSessionEJB
      Section: 16.2
      Warning: The Bean Provider must specify the fully-qualified name of the enterprise bean's home interface in the home element.

      09:06:06,294 WARN [verifier] EJB spec violation:
      Bean : TestSessionEJB
      Section: 16.2
      Warning: The Bean Provider must specify the fully-qualified name of the enterprise bean's remote interface in the remote element

      then later the stacktrace:

      09:06:06,294 ERROR [MainDeployer] could not create deployment: file:/C:/jboss-4.0.2/server/default/deploy/ejb-app.jar
      org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.
      at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:553)........

      I have found entries of this message on the net, but none with a real resolution. Any ideas please? I notice there's not a great deal of content in the manifest -

      Manifest-Version: 1.0
      Ant-Version: Apache Ant 1.6.1
      Created-By: 1.5.0_04-b05 (Sun Microsystems Inc.)

      perhaps with is contributing? I am using JB 4.0.2 on Win XP.

      thanks

      Paul.

      <ejb-jar>
      <enterprise-beans>
      this is a test
      <display-name>Test</display-name>
      <ejb-name>TestSessionEJB</ejb-name>
      au.com.twtva.ejb.TestSessionHome
      au.com.twtva.ejb.TestSession
      <ejb-class>au.com.twtva.ejb.TestSessionBean</ejb-class>
      <session-type>Stateless</session-type>
      <transaction-type>Container</transaction-type>

      </enterprise-beans>
      </ejb-jar>

        • 1. Re: EJB deployment problem
          Erik Sliman Apprentice

          You're missing some XML. Try this:

          <ejb-jar>
          <enterprise-beans>
          this is a test
          <display-name>Test</display-name>
          <ejb-name>TestSessionEJB</ejb-name>
          <home>au.com.twtva.ejb.TestSessionHome</home>
          <remote>au.com.twtva.ejb.TestSession</remote>
          <ejb-class>au.com.twtva.ejb.TestSessionBean</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Container</transaction-type>
          
          </enterprise-beans>
          </ejb-jar>
          


          You need to use the home and remote tags.

          • 2. Re: EJB deployment problem
            Paul Wallace Newbie

            hi & thanks,
            The home and remote tags along with description had their tags stripped when rendering on the HTML page! Very odd. Here is the XML, spaced, which will hopefully render it as it is packaged:

            <ejb-jar>
            <enterprise-beans>

            < description >this is a test< /description >
            <display-name>Test</display-name>
            <ejb-name>TestSessionEJB</ejb-name>
            < home >au.com.twtva.ejb.TestSessionHome< / home>
            < remote >au.com.twtva.ejb.TestSession< /remote >
            <ejb-class>au.com.twtva.ejb.TestSessionBean</ejb-class>
            <session-type>Stateless</session-type>
            <transaction-type>Container</transaction-type>

            </enterprise-beans>
            </ejb-jar>

            • 3. Re: EJB deployment problem
              Paul Wallace Newbie

              P.S the XML rendered OK this time! It was validated as per the DTD using my IDE. Any further thoughts please? What should be contained in the manifest?

              many thanks

              Paul.