[cdi-dev] [JBoss JIRA] (CDI-245) Promote the right way how extensions should communicate with each other during container initialization
[
https://issues.jboss.org/browse/CDI-245?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-245:
-----------------------------------
I don't agree with your quote - you took the EDR-1.1 version already ;)
{quote}
If other beans are injected into service providers, non-portable behavior results.
{quote}
This sentence is not present in CDI-1.0 :)
PS: I'm not sure about 'the ApplicationContext is always active'. See 6.7.3.
"Application context lifecycle" and especially 11.5.3.
"AfterDeploymentValidation event":
{quote}
The container must fire a third event after it has validated that there are no deployment
problems and before creating contexts or processing requests.
{quote}
Could be something we need to clarify.
Promote the right way how extensions should communicate with each
other during container initialization
-------------------------------------------------------------------------------------------------------
Key: CDI-245
URL: https://issues.jboss.org/browse/CDI-245
Project: CDI Specification Issues
Issue Type: Clarification
Affects Versions: 1.0, 1.1.EDR1
Reporter: Martin Kouba
Fix For: 1.1 (Proposed)
This is not clear right now. The spec allows (does not forbid) extensions to fire regular
events via {{BeanManager}} and I believe this should be _the right way_. See also CDI-109
discussion. However we should also state that extensions _may not fire container lifecycle
events_ as this could lead to unexpected results (and it's pretty broken imho).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira