[cdi-dev] [JBoss JIRA] (CDI-623) Specify what happens when calling addObserverMethod or addBean alone

Matej Novotny (JIRA) issues at jboss.org
Mon Jul 11 04:01:00 EDT 2016

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

Matej Novotny commented on CDI-623:

Are you talking about the spec doc or javadoc?
It seems to me that the [javadoc|https://github.com/cdi-spec/cdi/blob/2.0-EDR2/api/src/main/java/javax/enterprise/inject/spi/AfterBeanDiscovery.java#L82] is pretty clear on this.
The configuration is not reusable and that was talked through a thousand times. The idea is that every call of {{abd.add*()}} gives you a new configurator and once you exit the observer method call, it will create a respective bean or observer method.

I cannot really see any 'dangling' configuration in this flow. Could you elaborate a bit please?

> Specify what happens when calling addObserverMethod or addBean alone
> --------------------------------------------------------------------
>                 Key: CDI-623
>                 URL: https://issues.jboss.org/browse/CDI-623
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>            Reporter: John Ament
> AfterBeanDiscovery exposes methods addObserverMethod and addBean.  Both essentially leave dangling configurations that are not usable.
> I'd like for this ticket to clarify what happens in those dangling cases, or in cases where a configuration is completed.

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list