[cdi-dev] [JBoss JIRA] (CDI-726) Deprecate before dropping CDI.setCDIProvider

Emily Jiang (JIRA) issues at jboss.org
Sun Jun 3 18:58:00 EDT 2018

    [ https://issues.jboss.org/browse/CDI-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585889#comment-13585889 ] 

Emily Jiang commented on CDI-726:

OSGi runtime integator uses this. Romain, as explained by Martin, it is not
designed by lib usage. Can you elaborate your use case here so that we can
discuss further?


On Tue, May 29, 2018 at 4:24 PM, Martin Kouba (JIRA) <issues at jboss.org>

Emily Jiang
ejiang at apache.org

> Deprecate before dropping CDI.setCDIProvider
> --------------------------------------------
>                 Key: CDI-726
>                 URL: https://issues.jboss.org/browse/CDI-726
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Java SE Integration
>    Affects Versions: 2.0 .Final
>            Reporter: Romain Manni-Bucau
>            Priority: Blocker
> CDI.setCDIProvider allows to switch the cdi provider at *any* time by *anyone*. This lead to issues integrating multiple libraries doing it + is not a real user facing API, it is actually a server internal.
> Proposal is to deprecate the method, remove its implementation (always throw an IllegalStateException or just do a noop) and finally drop the method after one or two releases since it can't really be used except for very simple apps.

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list