1 Reply Latest reply on Apr 29, 2004 2:51 PM by sys user

    strange deployment

    sys user Master

      Hello,

      I have a strange deployment. I have all CMP 2 Entity beans defined with local interface. In ejb-jar.xml file I use tags local and local-home. But on the deployment of the ear file I see the following

      2004-04-29 12:00:30,468 INFO [org.jboss.ejb.EjbModule] Deploying AEntity
      2004-04-29 12:00:30,468 INFO [org.jboss.ejb.EjbModule] Deploying BEntity
      :
      :
      2004-04-29 12:00:48,473 INFO [org.jboss.ejb.plugins.EntityInstancePool] Started jboss.j2ee:jndiName=AEntity,plugin=pool,service=EJB
      2004-04-29 12:00:48,474 INFO [org.jboss.ejb.EntityContainer] Started jboss.j2ee:jndiName=AEntity,service=EJB
      2004-04-29 12:00:48,541 INFO [org.jboss.ejb.plugins.EntityInstancePool] Started jboss.j2ee:jndiName=local/BEntity,plugin=pool,service=EJB
      2004-04-29 12:00:48,543 INFO [org.jboss.ejb.EntityContainer] Started jboss.j2ee:jndiName=local/BEntity,service=EJB
      :
      :
      


      You might observe here that "AEntity" has jndiName "AEntity", where as "BEntity" has jndiName "local/BEntity". Because of this my lookups are not working. For some entities I have to use just the ejb-name where as for others I need to use local/ejb-name.

      Can anyone please point out what could be wrong?

      I am using JBoss 3.2.3 on Linux with Sun JDK 1.4.2_04

      Thanks in advance

      -VM

        • 1. Re: strange deployment
          sys user Master

          Found the problem. In my jboss.xml where I defined the entities to be Instance Per Transaction; I forgot to add the JNDI NAME tag. Other entities had the JNDI NAME tag. And hence some entity beans had JNDI NAME pattern different than others.

          -VM