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

Thu Aug 16 04:53:14 EDT 2012

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

Mark Struberg commented on CDI-245:
-----------------------------------

I took another route for a DeltaSpike extension.

It's perfectly valid to @Inject an Extension into another, e.g. in the @Observes BeforeBeanDiscovery. That way you can perfectly interact with known other Extensions.

Btw, this should also be considered when fixing the 'what beans can be injected at container boot'. It's not only the BeanManager but all internal beans (really all? e.g. Contexts?) + the Extensions which are Beans per the spec if I remember correctly.

> 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