[
https://jira.jboss.org/jira/browse/WBRI-332?page=com.atlassian.jira.plugi...
]
Pete Muir resolved WBRI-332.
----------------------------
Resolution: Done
Assignee: Pete Muir
Ken, I've made some changes (see
http://fisheye.jboss.org/browse/Webbeans/ri/trunk/spi/src/main/java/org/j...),
so that the bootstrap phases match the phases defined in the spec (with the additional
startContainer phase, which I need for tests). Please close this issue if you are happy
with the new API, or reopen if you want other changes...
Thanks!
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