]
jaikiran pai resolved EJBTHREE-2181.
------------------------------------
Component Fix Version(s): jboss-ejb3-jndi:0.1.2
Fix Version/s: depchain-1.0.0
Resolution: Done
EJBBinder doesn't bind to the additional JNDI name in the
presence of just a single view for EJB
------------------------------------------------------------------------------------------------
Key: EJBTHREE-2181
URL:
https://jira.jboss.org/browse/EJBTHREE-2181
Project: EJB 3.0
Issue Type: Bug
Components: jndi
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: depchain-1.0.0
The EJB3.1 spec (section 4.4.1) says this:
In addition to the previous requirements, if the bean exposes only one of the applicable
client interfaces(or alternatively has only a no-interface view), the container registers
an entry for that view with the following syntax :
java:global[/<app-name>]/<module-name>/<bean-name>
The container is also required to make session bean JNDI names available through the
java:app and java:module namespaces.
The EJBBinder currently doesn't bind to this additional JNDI name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: