[
https://issues.jboss.org/browse/CDI-711?page=com.atlassian.jira.plugin.sy...
]
Matej Novotny edited comment on CDI-711 at 8/17/17 4:48 AM:
------------------------------------------------------------
Looks like a valid use case we missed.
-Just thinking whether there wasn't some kind of a problem with defining an enabled
alternative this late in the bootstrap process?-
EDIT: Shouldn't cause any troubles as it is really just a twist on a custom bean with
{{@Prioritized}}.
Also, how about adding another method which would allow you to declare the bean as
alternative while selecting it at the same time - {{alternativeWithPriority(int
priority)}}?
was (Author: manovotn):
Looks like a valid use case we missed.
Just thinking whether there wasn't some kind of a problem with defining an enabled
alternative this late in the bootstrap process?
BeanConfigurator cannot be used to define alternative beans enabled
for an application
---------------------------------------------------------------------------------------
Key: CDI-711
URL:
https://issues.jboss.org/browse/CDI-711
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Portable Extensions
Affects Versions: 2.0 .Final
Reporter: Martin Kouba
Fix For: 2.1 (Discussion)
Custom bean implementations may implement {{Prioritized}} interface. There should be
probably a {{BeanConfigurator.priority(int priority)}} method.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)