[cdi-dev] [JBoss JIRA] (CDI-711) BeanConfigurator cannot be used to define alternative beans enabled for an application
Matej Novotny (JIRA)
issues at jboss.org
Mon Aug 14 07:47:00 EDT 2017
[ https://issues.jboss.org/browse/CDI-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448359#comment-13448359 ]
Matej Novotny commented on CDI-711:
-----------------------------------
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)
More information about the cdi-dev
mailing list