2 Replies Latest reply on Feb 27, 2002 10:29 PM by Marcus Brito

    Entity CMP bean not seen in JNDI Namespace - why?

    Eric Newbie

      I have a basic entity bean deployed through the autodeployer. The trace gives me the following. I assume that everything goes well.


      INFO ejb.AutoDeployer - Auto deploy of file:/C:/Development/jboss/JBoss-2.4.4_Tomcat-4.0.1/jboss/deploy/entity.jar
      INFO deployment.J2eeDeployer - Deploy J2EE application: file:/C:/Development/jboss/JBoss-2.4.4_Tomcat-4.0.1/jboss/deploy/entity.jar
      INFO deployment.J2eeDeployer - Create application entity.jar
      INFO deployment.J2eeDeployer - install EJB module entity.jar
      INFO ejb.ContainerFactory - Deploying:file:/C:/Development/jboss/JBoss-2.4.4_Tomcat-4.0.1/jboss/tmp/deploy/Default/entity.jar/
      DEBUG ejb.ContainerFactory - Verifying file:/C:/Development/jboss/JBoss-2.4.4_Tomcat-4.0.1/jboss/tmp/deploy/Default/entity.jar/ejb1009.jar
      INFO ejb.ContainerFactory - Deploying DemoEntity
      DEBUG plugins.EntityInstancePool - config - MaximumSize=100, strictMaximumSize=false, feederPolicy=null
      DEBUG local.BaseLocalContainerInvoker - Caching methods for localClass: interface entity.demo.LocalEntity
      DEBUG local.BaseLocalContainerInvoker - Caching methods for localHomeClass: interface entity.demo.LocalEntityHome
      DEBUG ejb.EntityContainer - Begin java:comp/env for EJB: DemoEntity
      DEBUG ejb.EntityContainer - TCL: java.net.URLClassLoader@9d96b1
      DEBUG ejb.EntityContainer - End java:comp/env for EJB: DemoEntity
      DEBUG jaws.JAWSPersistenceManager - Initializing JAWS plugin for DemoEntity
      DEBUG jaws.JAWSPersistenceManager - Loading standardjaws.xml : file:/C:/Developm
      DEBUG jaws.JAWSPersistenceManager - AutoGenerated finders - Home=null -- LocalHome=interface entity.demo.LocalEntityHome
      DEBUG jaws.JAWSPersistenceManager - Save AutoGenerated findByName public abstract java.util.Collection entity.demo.LocalEntityHome.findByName(java.lang.String)
      throws javax.ejb.FinderException
      DEBUG jaws.JAWSPersistenceManager - Finder:name
      DEBUG jaws.JAWSPersistenceManager - Table DemoEntity created
      INFO jaws.JAWSPersistenceManager - Created table 'DemoEntity' successfully.
      DEBUG jaws.JAWSPersistenceManager - Primary key of table 'DemoEntity' is 'localId'
      INFO ContainerManagement.DemoEntity - Initializing
      INFO ContainerManagement.DemoEntity - Initialized
      INFO ContainerManagement.DemoEntity - Starting
      INFO ContainerManagement.DemoEntity - Started
      INFO ejb.ContainerFactory - Deployed application: file:/C:/Development/jboss/JBoss-2.4.4_Tomcat-4.0.1/jboss/tmp/deploy/Default/entity.jar/
      INFO deployment.J2eeDeployer - J2EE application: file:/C:/Development/jboss/JBoss-2.4.4_Tomcat-4.0.1/jboss/deploy/entity.jar is deployed.
      INFO ejb.AutoDeployer - Auto undeploy of file:/C:/Development/jboss/JBoss-2.4.4_Tomcat-4.0.1/jboss/deploy/entity.jar
      DEBUG plugins.LRUEnterpriseContextCachePolicy - Resized cache for bean DemoEntity: old capacity = 1000, new capacity = 50


      Now when I query the JNDI Namespace via the admin, I can just see the application reference:
      java:comp namespace of the DemoEntity bean:

      +- env (class: org.jnp.interfaces.NamingContext)

      but I do not see it in the Namespace.

      In the META-INF directory of my archive, the file jboss.xml specifies the following:

      <container-configurations />
      <resource-managers />



      and my ejb-jar is:


      no description
      no description
      no description


      <ejb-ql>select object(u) from Demo u where u.name = ?1</ejb-ql>





      Any idea of why this EJB is not visible?
      Of course, any attempt from a client to access it fails...

      Obviously, I'm doing something wrong, but what?

        • 1. Re: Entity CMP bean not seen in JNDI Namespace - why?
          Eric Newbie

          Ok, I found where the problem was:

          this is not supported by JBOSS apparently. This works well in the j2ee sdk (and actually this was created by it). Don't why exactly when you think twice since this directive <local-home> and explicitely call for local objects... (not sure, just guessing).

          I did the following:
          Changed my interfaced so that they inherit from EJBObject and EJBHome
          and declared them as
          ... ...

          Now my EJB is accessible

          • 2. Re: Entity CMP bean not seen in JNDI Namespace - why?
            Marcus Brito Novice

            Perhaps you should study a bit more about J2EE. What you did was replace your local interface by remote interfaces. This has many implications. Take a look at the EJB standard for more info.

            By the way, JBoss 2.4.x supposedly support local interfaces, but in som cryptic way that I couldn't figure out. JBoss 3.0.0 supports local interfaces nice and clean.