[weld-issues] [JBoss JIRA] Updated: (WELD-605) Give extensions access to the servlet context

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/browse/WELD-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir updated WELD-605:
---------------------------

                  Summary: Give extensions access to the servlet context  (was: add beforeContextInitialized and other servlet event)
            Fix Version/s:     (was: 1.1.0.BETA1)
              Description: It would be useful for extensions on a Servlet Container to be able to access the ServletContext somehow  (was: Sometimes i want to get ServletContextEvent weld event after weld container started and before validateBeans,so i can do some init work in weld extension.And I can wrap servletContext as a weld bean in this weld event's observe then i can use the servletContext bean in all weld extension of event's observe after 
container started.So we can do more init work of servlet container such as tomcat or jetty servlet inject or spring's init work.

see http://seamframework.org/Community/ShouldSeamServletEventMoveToWeldservletinit)
    JBoss Forum Reference: http://seamframework.org/Community/ShouldSeamServletEventMoveToWeldservletinit


Rewrite issue, and de-schedule, this is pretty hard to do.

> Give extensions access to the servlet context
> ---------------------------------------------
>
>                 Key: WELD-605
>                 URL: https://jira.jboss.org/browse/WELD-605
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Servlet Container Support
>            Reporter: he youlin
>
> It would be useful for extensions on a Servlet Container to be able to access the ServletContext somehow

-- 
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