Per EJB or EJB Interface JNDI Name declaration

• Key: OPENEJB-253
• Type: New Feature
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: David Blevins
• Reporter: Mohammad Nour
• Component/s: ejb3 simplified
• Affects Version/s: 3.0-beta-1
• Fix Version/s: 3.0-beta-2

Description

1- The current implementation of OEJB prefixes the JNDI names of local Home interface of an EJB by the word *Local*, that is the client would not expect to use when he\she tries to look up the bean.

2- When and EJB3.0 bean supports the backward compatible 2.1 Home interface and business interface, there is no way to specify separate JNDI names to each interface.

We should make the client being able to do this. One way is to make changes to the openejb-jar.xml schema to add new elements and attributes to give the client this ability, an example of an *ejb-deplyment* is as follows:

<ejb-deployment ejb-name="ExampleStatelessBean" container-id="Default Stateless Container">
      
    <deployment-id
               jndi-name="client/tests/stateless/BasicStatelessHomeInterface"
               interface-name="ejb3.beans.interfaces.BeanLocalHomeInterface" />
 
    <deployment-id
               jndi-name="client/tests/stateless/BasicStatelessBizInterface"
               interface-name="ejb3.beans.interfaces.BeanLocalBizInterface" isRemote="false" />
 
</ejb-deployment>

Comments will be added as soon as we agree upon how to tackle this problem.

Comments

[Mohammad Nour]

The latest suggestion from DBlevins is:

<ejb-deployment deployment-id="SomeBean" ...>
  <jndi-name interface="some.bean.SomeBeanLocalHomeInterface">some/jndi/name/SomeBeanLocalHome</jndi-name>
  <jndi-name interface="some.bean.SomeBeanRemoteHomeInterface">some/jndi/name/SomeBeanRemoteHome</jndi-name>
  <jndi-name interface="some.bean.SomeBeanRemoteBusinessInterface">some/jndi/name/SomeBeanRemoteBizIntfc</jndi-name>
  <jndi-name interface="some.bean.SomeBeanLocalBusinessInterface">some/jndi/name/SomeBeanLocalBizIntfc</jndi-name>
</ejb-deployment>

I give +1 on that and I think it is the best one till now.

[David Blevins]

$ svn ci
Sending container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/EnterpriseBeanInfo.java
Sending container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/JndiBuilder.java
Adding container/openejb-core/src/main/java/org/apache/openejb/assembler/classic/JndiNameInfo.java
Sending container/openejb-jee/src/main/java/org/apache/openejb/jee/oejb3/EjbDeployment.java
Adding container/openejb-jee/src/main/java/org/apache/openejb/jee/oejb3/Jndi.java
Transmitting file data .....
Committed revision 592489.

Added this format to the openejb-jar.xml :
<jndi name="foo" interface="org.acme.Foo"/>

Or more generally...
<jndi name="foo" interface="Remote"/>

Or more generally still...
<jndi name="foo"/>

The 'name' attribute can still use templates if it likes, such as:
<jndi name="ejb/{interfaceClass.simpleName}" interface="org.acme.Foo"/>