[
https://issues.jboss.org/browse/CDI-114?page=com.atlassian.jira.plugin.sy...
]
Vincent Massol commented on CDI-114:
------------------------------------
Hi guys. I was wondering if there was now a recommended way of supporting the main use
case I listed above back in 2011, namely:
If you have a CDI application, how can you add support for installing extensions at
runtime for this application (for example by adding JARs containing beans to the
classloader), and tell the Bean Manager to take into account those news beans?
I suspect this is a common need for apps as they grow (i.e. the ability to dynamically add
extensions). As I mentioned back then, we've been supporting this in XWiki for about
10 years now with our custom handmade solution but I hate using custom solutions when
there exists standard solutions so I'm always on the lookout for such solutions.
I've been wanting to try to use CDI for years now but have dropped it in 2011 because
of the lack of a solution.
The only option I've heard so far would be to tell the Bean Manager to
"restart" and thus re-run the process of creating/resolving the Bean graph. Is
that still the only solution? However, I'm worried that this would take too long for
our needs since XWiki has thousands (possibly tens of thousands) of Beans running, coming
from hundreds of JAR files. Is this "restart"/"reload" already
implemented and optimized so that there's no rescanning of JAR files for example? Does
anyone have any experience with this?
Thanks a lot!
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 was sent by Atlassian JIRA
(v7.2.3#72005)