[ https://issues.jboss.org/browse/CDI-726?page=com. atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel&focusedCommentId=13583731#comment-13583731 ] Martin Kouba commented on CDI-726: ---------------------------------- Hm, in CDI 1.2 it was only possible to set the provider once and I remember there was some legal use case for this method (OSGi or something like that). You're right that in CDI 2.0 anyone can set it anytime. The logic seems to be modified in this commit: https://github.com/cdi-spec/ cdi/commit/14cd36abb4d039212cf21521a46755b15f4e0a1c#diff- 03e83766e93415c9ba16a9dfb42a5ac5. [~antoinesabot-durand] Do you remember the details? > 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 (v7.5.0#75005) _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/ licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.