[
https://issues.jboss.org/browse/CDI-179?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-179:
-------------------------------
This is very hard to address as Java EE doesn't provide for a JNDI environment in non
Java EE components.
I believe this is better addressed by CDI-14.
Deferring as TBD.
Relax requirements for obtaining a BeanManager reference from JNDI
------------------------------------------------------------------
Key: CDI-179
URL:
https://issues.jboss.org/browse/CDI-179
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Portable Extensions
Affects Versions: 1.0
Reporter: Jozef Hartinger
Fix For: 1.1 (Proposed)
The spec says:
{quote}Java EE components may obtain an instance of BeanManager from JNDI by looking up
the name java:comp/BeanManager.{quote}
This is limiting since extensions often need to get a BeanManager reference from a
*non-EE* component, e.g.:
*
https://github.com/seam/solder/blob/develop/impl/src/main/java/org/jboss/...
*
https://resteasy.svn.sourceforge.net/svnroot/resteasy/trunk/jaxrs/resteas...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira