JNDI naming conflicts


General J2EE: JNDI naming conflicts

  1. JNDI naming conflicts (3 messages)


    I develop an EJB application with the following structure:
    I will at most have 2 different applications.
    One of them (AdminApp) will only deployed once and the other one (call it PlantApp) should be deployed several times. Their purpose is to manage several production plants. Each has its own J2EE app.
    As some of you already answered my question about EJB-EJB comm between different machines, I now have another problem.
    Is there an elegant way to simulate this scenario on a single machine. I am using J2EE RI 1.3.1.

    To be more precise: Let's say I have an AdminSession, an AdminEntity and a ProductEntity bean that all reside in AdminApp. In the PlantApp I also have the same ProductEntity bean along with a PlantSession an other entity bean. Now I'd like to deploy AdminApp once and PlantApp several times on my single maching. What about the conflicts between all the ProductEntity beans in the apps.
    Not to mention the other beans. I'd give ProductBean a JNDI name of 'Product'. How can I achieve (if possible at all), that the PlantApp PA1 uses it's own Product bean and not the Product bean that belongs to PlantApp PA2 or AdminApp?
    I know, they could use all the same entity, but the different apps should also use different DB resources for ProductEntity. Is there a smart way do achieve this without renaming JNDI names for every app to avoid naming conflicts.


    Threaded Messages (3)

  2. JNDI naming conflicts[ Go to top ]

    change the EJB's JNDI name in each application.
  3. JNDI naming conflicts[ Go to top ]

    You can change the ejb's jndi name.
    or run the ejb server more than one instance.Because Each instance have a deffrence port number .
  4. JNDI naming conflicts[ Go to top ]


    can I run several instances of the J2EE RI, too?
    What config files do I have to change?