[cdi-dev] [JBoss JIRA] (CDI-114) Allow registration of beans at runtime

Mark Struberg (Commented) (JIRA) jira-events at lists.jboss.org
Wed Nov 16 09:20:41 EST 2011

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

Mark Struberg commented on CDI-114:

Hi Vince!

Will need to sleep over it, but currently this looks more like a 'hot redeploy' than a real 'dynamic Bean' change. The problem with allowing to add dynamic Beans is that they e.g. can also 'disable' other Beans, change Interceptors, Decorators, etc. So by adding one Bean, you might in the worst case change the behaviour of all the application. 

Another area which we need to clarify: what happens if a definition error occurs as result of adding such a new bean? It would also be very hard (or close to almost impossible) to guarantee the behaviour of previously serialized beans.

I'm not saying that it's impossible, but we must really think about the consequences and how to cope with them.
> Allow registration of beans at runtime
> --------------------------------------
>                 Key: CDI-114
>                 URL: https://issues.jboss.org/browse/CDI-114
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Beans
>    Affects Versions: 1.0
>            Reporter: Vincent Massol
>             Fix For: TBD
> I have use cases where I need to register a bean dynamically at runtime (see the forum reference link for a detailed description of the use case).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the cdi-dev mailing list