[
https://jira.jboss.org/browse/EJBTHREE-2180?page=com.atlassian.jira.plugi...
]
jaikiran pai updated EJBTHREE-2180:
-----------------------------------
Summary: EJB3.1 spec jndi binder should not assume JBossSessionBean31MetaData
(was: EJB3.1 spec jndi binder should only apply for EJB3.1 beans)
Description:
The EJB3.1 spec doesn't specify the version to which the global jndi name spec
applies. We should consider both EJB3.0 and EJB3.1 session beans. As such, we should _not_
assume the metadata to be of type JBossSessionBean31MetaData.
was:
Currently, we even include EJB3.0 beans during EJBBinder creation. Only EJB3.1 beans
should be eligible.
EJB3.1 spec jndi binder should not assume JBossSessionBean31MetaData
--------------------------------------------------------------------
Key: EJBTHREE-2180
URL:
https://jira.jboss.org/browse/EJBTHREE-2180
Project: EJB 3.0
Issue Type: Bug
Reporter: jaikiran pai
Assignee: jaikiran pai
The EJB3.1 spec doesn't specify the version to which the global jndi name spec
applies. We should consider both EJB3.0 and EJB3.1 session beans. As such, we should _not_
assume the metadata to be of type JBossSessionBean31MetaData.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira