[
https://issues.jboss.org/browse/CDI-623?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-623:
----------------------------------
I'm not sure we should specify this. But if we do then we should probably use the same
requirements/validation rules for non-configurator methods as well, e.g. for
{{AfterBeanDiscoveryImpl.addBean(Bean<?>)}}. Actually, in Weld we already do some
simple validation and e.g. throw {{DefinitionException}} if {{getBeanClass()}} returns
null.
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)