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

[Matej Novotny (JIRA)]

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

Matej Novotny commented on CDI-623:
-----------------------------------

I am fine with saying that obtaining a configurator without doing actual work doesn't make sense and we should throw an exception (ISE most likely).
However I am not convinced we should describe the minimum info as that can get pretty complex especially if combined with {{read}} methods. (Which sort of leads to https://issues.jboss.org/browse/CDI-614)

> 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
>              Labels: F2F2016
>             Fix For: 2.0 (discussion)
>
>
> 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
(v6.4.11#64026)