2 Replies Latest reply on Oct 8, 2003 9:00 AM by gimi

    session bean (ejb-jar.xml)

    gimi

      Hello,

      My application runs by now with JBoss 3.0!
      Trying to run under JBoss 3.2.1 I got some
      errors:
      ============================
      16:47:33,887 WARN [verifier] EJB spec violation:
      Bean : RecorderSvcSkin
      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.

      16:47:33,887 WARN [verifier] EJB spec violation:
      Bean : RecorderSvcSkin
      Section: 16.2
      Warning: The Bean Provider must specify the fully-qualified name of the enterprise bean's remote interface in the remote element.
      ===========================

      The description in ejb-jar.xml looks like this:

      ===========================

      Recorder for SvcSkin.
      <display-name>RecorderSvcSkin Bean</display-name>
      <ejb-name>RecorderSvcSkin</ejb-name>
      bbt.cn.core.service.SvcSkinHome
      bbt.cn.core.service.SvcSkin
      <ejb-class>bbt.test.service.RecorderSvcSkinImpl</ejb-class>
      <session-type>Stateless</session-type>
      <transaction-type>Container</transaction-type>

      ===========================

      Anybody have any idea how to solve this problem??

      gimi

        • 1. Re: session bean (ejb-jar.xml)

          How are you packaging your app? might be a classloader visibility problem, there's been a fix to that rather recently, is it possible for you to try with the latest 3.2.2RC4 and see if it has the same problem?

          -- Juha

          • 2. Re: session bean (ejb-jar.xml)
            gimi

            I solved the problem! It was not jboss-problem but my mistake! I didn't pack everything correctly and jboss didn't found the classes!

            So now I have another question,

            When I start JBoss, it takes very long until it creates a PersistenceManager (PM)! The default PM by JBoss 3.2.1 is jdbc2 "org.jboss.mq.pm.jdbc2.PersistenceManager" (by JBoss 3.0 it was the file PersistentManager "org.jboss.mq.pm.file.PersistenceManager") and it was not that slow.

            My problem is now, that when I use another PM (file-PM or rolling-PM) then JBoss fails to start MessageCashe!
            I also uncommented the optional atribute "CasheStore" but vainly!

            thanx,
            gimi