[
https://issues.jboss.org/browse/CDI-114?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-114:
-----------------------------------
Actually not supporting beans which can dynamically change at runtime is a BIG benefit. We
are now >30 times faster than Spring3 core, mostly because of the ability to
aggressively cache intermediate results. If we would support dynamic beans, then we would
need to re-evaluate all bits from the very bottom, basically starting with picking up all
annotations and meta-info for each and every method invocation to a bean (as spring does
today) I already know big customers which moved over to CDI because of that.
Of course we might introduce some support for hot-deployment which can be triggered (and
would then stale the whole app for that timeframe).
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