[cdi-dev] [JBoss JIRA] Commented: (CDI-117) Add BeanManager to a ServletContext attribute
Dan Allen (JIRA)
jira-events at lists.jboss.org
Mon Apr 18 12:01:33 EDT 2011
[ https://issues.jboss.org/browse/CDI-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596241#comment-12596241 ]
Dan Allen commented on CDI-117:
For clarification, the reason Weld changed the name is because we decided (I think) that Seam Servlet (and Seam Faces) would put the BeanManager into the proposed standard attribute.
We are using the FQCN of BeanManager, javax.enterprise.inject.spi.BeanManager.
> Add BeanManager to a ServletContext attribute
> Key: CDI-117
> URL: https://issues.jboss.org/browse/CDI-117
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Java EE integration
> Affects Versions: 1.0
> Reporter: Christian Kaltepoth
> Priority: Minor
> CDI 1.0 defines a JNDI lookup as the standard way to obtain the BeanManager for resources not managed by the CDI environment. However in a servlet environment it would be much easier to get the BeanManager from a standardized servlet context attribute. This would be also a major simplification in environments that don't support JNDI (for example GAE) or that don't allow to use the standard JNDI name for the BeanManager (for example Apache Tomcat).
> This topic was already discussed on weld-dev about a year ago . Weld 1.0 already supports this  and OpenWebBeans also added this feature . Unfortunately Weld 1.1 changed the attribute to a Weld-specific name in  which currently leads to much confusion .
> As both of the major CDI implementations support this feature I think it should finally be put into the spec.
>  http://lists.jboss.org/pipermail/weld-dev/2010-March/002359.html
>  https://issues.jboss.org/browse/WELD-202
>  https://issues.apache.org/jira/browse/OWB-360
>  https://jira.jboss.org/browse/WELD-679
>  http://seamframework.org/Community/GettingBeanManagerFromServletContextWithWeld11
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the cdi-dev