[cdi-dev] [JBoss JIRA] (CDI-245) Promote the right way how extensions should communicate with each other during container initialization

[Pete Muir (JIRA)]

    [ https://issues.jboss.org/browse/CDI-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713672#comment-12713672 ] 

Pete Muir commented on CDI-245:
-------------------------------

Interestingly, the quote does say "may observe any event", which supports [~mkouba] original point.

I think we can close this issue out by saying:

* If a portable extension fires a container lifecycle event, non-portable behavior results
* That an extension can fire a regular event by calling BeanManager.fireEvent()
* Opening a new issue around contexts being active during bootstrap, as we don't really need that, as extensions are not defined as beans, but as objects which can take advantage of some CDI capabilities

I'll draft up these changes and open a new issue.
                
> 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.EDR
>            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