February 2017 - cdi-dev - Jboss List Archives

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

by Samba Siva Rao Kolusu (JIRA)

[ https://issues.jboss.org/browse/CDI-682?page=com.atlassian.jira.plugin.sy... ] Samba Siva Rao Kolusu updated CDI-682: -------------------------------------- Description: much like the ability to register beans at runtime through API (https://issues.jboss.org/browse/CDI-114) also provide API BeanManager::unregister("beanName"), or BeanManager::unregister(XYZBean.class) to unregister beans at runtime, and corresponding events (BeforeUnregisteringBean, AfterUnregisteringBean, etc) so that interested listeners can take appropriate actions in the event of a bean getting removed from CDI context. these two together will help build pluggable web applications much like OSGI modules. right now, installing new beans or removing exiting beans requires restart of CDI container, if not web application. with the addition of these two features [registering beans at run time, through BeanManager::register(XYZBean.class) ], and unregistering beans at runtime [BeanManager::unregister(XYZBean.class) ] true modularity comes to Java EE world, without the necessity to restart > 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 > > much like the ability to register beans at runtime through API (https://issues.jboss.org/browse/CDI-114) > also provide API > BeanManager::unregister("beanName"), or BeanManager::unregister(XYZBean.class) > to unregister beans at runtime, and corresponding events (BeforeUnregisteringBean, AfterUnregisteringBean, etc) so that interested listeners can take appropriate actions in the event of a bean getting removed from CDI context. > these two together will help build pluggable web applications much like OSGI modules. right now, installing new beans or removing exiting beans requires restart of CDI container, if not web application. with the addition of these two features [registering beans at run time, through BeanManager::register(XYZBean.class) ], and unregistering beans at runtime [BeanManager::unregister(XYZBean.class) ] true modularity comes to Java EE world, without the necessity to restart -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 11 months

1
0
0 / 0

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

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-682?page=com.atlassian.jira.plugin.sy... ] 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)

7 years, 11 months

1
0
0 / 0

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

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/CDI-682?page=com.atlassian.jira.plugin.sy... ] Matej Novotny commented on CDI-682: ----------------------------------- 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)

7 years, 11 months

1
0
0 / 0

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

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/CDI-682?page=com.atlassian.jira.plugin.sy... ] Tomas Remes commented on CDI-682: --------------------------------- Hi [~saasira] Could you be please more specific? > 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)

7 years, 11 months

1
0
0 / 0

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

by Samba Siva Rao Kolusu (JIRA)

Samba Siva Rao Kolusu created CDI-682: ----------------------------------------- Summary: 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)

7 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev February 2017