[
https://issues.jboss.org/browse/CDI-114?page=com.atlassian.jira.plugin.sy...
]
Vincent Massol commented on CDI-114:
------------------------------------
[~rmannibucau] If we need to keep our XWiki Component Manager then there's little
interest in moving to CDI since (if I understand correctly) we would be able to use the
CDI features only for core components that are registered statically at application boot
time (and thus have two distinct Component models depending on whether you're coding a
core extension or a non-core one). We're also reducing our number of core components
to the maximum as time progresses to have the smallest possible core and all the rest are
extracted into extensions. We currently have hundreds of extensions and this will grow
even more in a very near future. So having 2 models is not a good idea IMO :)
{quote}but producers generally means 'do it yourself'{quote}
I don't understand this part. AFAIK you can use CDI constructs in producers, using
injections, qualifiers, etc. Aren't there plenty of CDI apps that use producer
constructs too without requiring to implement a Component Manager that would handle
instantiation/injection? If the object created in the producers requires to be injected
other beans, CDI doesn't provide any helper for that?
Thanks
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)