[
https://issues.jboss.org/browse/CDI-623?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-623:
------------------------------------------
I guess that [~meetoblivion] is talking of the case were a configurator is requested and
the user doesn't do anything with it.
That's good point, since the "build" method of these builder is hidden we
still have to specify what is the minimum info we have to add to these configurators to be
able to build them.
So we need:
# specify what is the minimum configuration user has to put in a {{BeanConfigurator}} and
{{ObserverMethodConfigurator}} to make them viable. Propbaly the same for toher
configurator
# what shoudl be the behaviour ot eh container in case of a non viable Configurator
(abd.add*()) was called and nothing (or non mimimum requirement) was done with the
returned configurator. ISE seems to be the best choice here
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
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)