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

Pete Muir (JIRA) jira-events at lists.jboss.org
Thu Aug 16 08:58:15 EDT 2012


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

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

No, this is well defined by the spec. See Section 11.5

{quote}
An extension is a service provider of the service javax.enterprise.inject.spi.Extension declared in META-INF/services. 

Service providers may have observer methods, which may observe any event, including any container lifecycle event, and obtain an injected BeanManager reference. If other beans are injected into service providers, non-portable behavior results.
{quote}
                
> 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

        


More information about the cdi-dev mailing list