[ https://issues.jboss.org/browse/CDI-179?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-179: -------------------------- Fix Version/s: TBD (was: 1.1 (Proposed)) -- 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

[ https://issues.jboss.org/browse/CDI-179?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-179: ----------------------------------- Actually it's not only JavaSE projects which have this problem. In my case I have a clean 3 tier architecture where my backend.jars have NO whatever servlet specific dependency! Just to prevent that some funny guy implements frontend parts in my backend.jar. So in a cleanly setup environment JNDI just entirely doesn't exist for 80% of of the code. So I would not really care about JNDI names for non EE environments, because most people will not be able to retrieve it anyway. CODI and Seam3 both already provide nice Classes to access the BeanManager in a portable way. (for CODI see: https://svn.apache.org/repos/asf/myfaces/extensions/cdi/trunk/core/api/sr...) -- 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