[cdi-dev] [JBoss JIRA] (CDI-682) Allow de-registration of CDI beans at run time, through API

[Matej Novotny (JIRA)]

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

Matej Novotny edited comment on CDI-682 at 2/1/17 7:15 AM:
-----------------------------------------------------------

Also de-registration sounds like an impossible feat because of the static nature of CDI.
Things are done at bootstrap and they stay that way during application runtime.
Imagine what would happen if you had a {{@Specializes}} bean and tried to de-register that one at runtime.

Furthermore, this would result in weird behaviour if you, say, de-register a session scoped bean during active session.


was (Author: manovotn):
Also de-registration sounds like an impossible feat because of the static nature of CDI.
Things are done at bootstrap and they stay that way in application runtime.
Imagine what would happen if you had a {{@Specializes}} bean and tried to de-register that one at runtime.

> Allow de-registration of CDI beans at run time, through API
> -----------------------------------------------------------
>
>                 Key: CDI-682
>                 URL: https://issues.jboss.org/browse/CDI-682
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Beans, Events, Interceptors
>    Affects Versions: 1.2.Final
>            Reporter: Samba Siva Rao Kolusu
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)