[ https://issues.apache.org/jira/browse/OPENEJB-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Blevins updated OPENEJB-253:
----------------------------------
Fix Version/s: (was: 3.0-beta-1)
3.0.x
Summary: Per EJB or EJB Interface JNDI Name declaration (was: We need to make
the client be able to explicitly define the JNDI names of different interfaces provided the
EJB)
> Per EJB or EJB Interface JNDI Name declaration
> ----------------------------------------------
>
> Key: OPENEJB-253
> URL: https://issues.apache.org/jira/browse/OPENEJB-253
> Project: OpenEJB
> Issue Type: New Feature
> Components: ejb3 simplified
> Affects Versions: 3.0-beta-1
> Reporter: Mohammad Nour
> Fix For: 3.0.x
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|