[webbeans-issues] [JBoss JIRA] Commented: (WBRI-332) Need more granular control of web beans discovery vs. sending of various initialization events

Ken Saks (JIRA) jira-events at lists.jboss.org
Tue Aug 11 10:11:29 EDT 2009


    [ https://jira.jboss.org/jira/browse/WBRI-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12480095#action_12480095 ] 

Ken Saks commented on WBRI-332:
-------------------------------

Looks good, thanks.  I assume we call endInitialization() after validateBeans() ?

> Need more granular control of web beans discovery  vs. sending of various initialization events
> -----------------------------------------------------------------------------------------------
>
>                 Key: WBRI-332
>                 URL: https://jira.jboss.org/jira/browse/WBRI-332
>             Project: Web Beans
>          Issue Type: Bug
>          Components: Bootstrap, Events, Glassfish integration
>         Environment: 1.0.0.PREVIEW2.SP2 in GlassFish V3 trunk
>            Reporter: Ken Saks
>            Assignee: Pete Muir
>             Fix For: 1.0.0.CR1
>
>
> In the current SPI, WebBeansBootstrap().bootstrap() performs web beans discovery and sends out any BeforeBeanDiscovery, AfterBeanDiscovery, and AfterDeploymentValidation events.   We need more granular control of these individual actions to match the deployment phases in GlassFish.    Other non-299 related initialization tasks need to take place after web beans discovery, so most important is to decouple the sending of the AfterDeploymentValidation event  so it can occur after the  EE application has made it through all initialization stages.   

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

        



More information about the weld-issues mailing list