[weld-issues] [JBoss JIRA] Resolved: (WELD-256) Bootstrap End Initialization May Not Complete Before ContextInitialized (Servlet)

[Pete Muir (JIRA)]

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

Pete Muir resolved WELD-256.
----------------------------

    Resolution: Done
      Assignee: Pete Muir


The container now has an initialized and unvalidated phase between the end of deployBeans() and the end of endInitialization(), the contextInitialized event can be called after deployBeans().

Please test

> Bootstrap End Initialization May Not Complete Before ContextInitialized (Servlet)
> ---------------------------------------------------------------------------------
>
>                 Key: WELD-256
>                 URL: https://jira.jboss.org/jira/browse/WELD-256
>             Project: Weld
>          Issue Type: Bug
>          Components: Bootstrap and Metamodel API, GlassFish Integration, Web Tier integration (JSF, JSP, EL and Servlet) 
>         Environment: mac, glassfish
>            Reporter: Roger Kitain
>            Assignee: Pete Muir
>             Fix For: 1.0.0.CR2
>
>
> Currently, in GlassFish we execute:
>     startContainer
>     startInitialization
>     deployBeans
> when an APPLICATION_LOADED event is received.
> And we execute:
>     validateBeans
>     endInitialization
> when an APPLICATION_STARTED event is received.
> This is problematic because weld expects the bootsrapping process (including endInitialization) to be complete
> by the time a servlet context initialized event is received.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira