[
https://issues.jboss.org/browse/CDI-623?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-623:
------------------------------------------
[~manovotn], [~mkouba], I think we are mixing 2 illegal state here:
* A defined bean that is illegal. This ticket shouldn't change nothing about this
* A bean to build thru a configurator that was not defined (which has no defined type set
or code to create instances).
Second case is our matter here. Now,I agree that it may be difficult to specify the
minimum required to have a configurator ready to create a defined bean. Anyway
implementation will have to do this.
Calling {{BeforeBeanDiscovery.addAnnotatedType()}} without using the returned configurator
should trigger an exception at the end of BBD invocation.
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)