]
arjan tijms commented on CDI-492:
---------------------------------
{quote}I understand those concerns, but I think there are solution for most of
them.{quote}
Just wondering if there's any progress here or someone still looking into this?
Like Antoine I can't help but feel the issues raised are worth looking into to see if
they can be solved. A part of the solution can simply be education, as perhaps it's
just a matter of not everyone being fully up to date with how CDI works.
Give ownership of servlet specific part to servlet specification
----------------------------------------------------------------
Key: CDI-492
URL:
https://issues.jboss.org/browse/CDI-492
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Java EE integration
Reporter: Antoine Sabot-Durand
Fix For: 2.0 (discussion)
[Section 3.8 of the
spec|http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#additional_builtin_...] places
some requirements on CDI implementations when running with Servlet. To better suit user
desires for modularity these requirements are better met by moving them to the Servlet
spec. Specifically,
{quote}
A servlet container must provide the following built-in beans, all of which have
qualifier @Default:
* a bean with bean type {{javax.servlet.http.HttpServletRequest}}, allowing injection of
a reference to the HttpServletRequest
* a bean with bean type {{javax.servlet.http.HttpSession}}, allowing injection of a
reference to the HttpSession,
* a bean with bean type {{javax.servlet.ServletContext}}, allowing injection of a
reference to the ServletContext,
These beans are passivation capable dependencies, as defined in Passivation capable
dependencies.
{quote}