[cdi-dev] [JBoss JIRA] (CDI-624) Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle

[John Ament (JIRA)]

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

John Ament commented on CDI-624:
--------------------------------

These methods must have snuck in.  I was pushing hard against the idea of mixing container init and lifecycle in SE.  I would prefer the dynamic extension approach, if anything were to be followed.

> Map SeContainerInitializer.addBeans() and SeContainerInitializer.addAnnotatedTypes() to the application initialization lifecycle
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CDI-624
>                 URL: https://issues.jboss.org/browse/CDI-624
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Java SE Integration
>    Affects Versions: 2.0-EDR2
>            Reporter: Martin Kouba
>
> I believe we should not break the application initialization lifecycle. 
> So it might be reasonable to state that {{SeContainerInitializer.addAnnotatedTypes()}} maps to {{AfterTypeDiscovery.addAnnotatedType(AnnotatedType<?>, String)}} (note that we would have to sort out missing id) and {{SeContainerInitializer.addBeans()}} maps to {{AfterBeanDiscovery.addBean(Bean<?>)}}.
> The other solution would be to remove these methods and introduce the concept of "synthetic container lifecycle event observers" and leverage the configurators API. See also http://weld.cdi-spec.org/news/2016/02/08/weld-se-synth-lifecycle-events/. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)