[
https://issues.jboss.org/browse/CDI-113?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on CDI-113:
-------------------------------
I may have lost you, but why are we talking about multiple BeanManager implementations?
There is only one BeanManager implementation, and that's the one provided by the
runtime environment (JBoss AS). If you see @Inject BeanManager, you just have to assume
that it's a valid injection point based on the rules of CDI. This is a much different
case than injecting an application-defined bean.
If I'm not understanding your concern, please let me know.
Add some design time readable metadata for built-in beans of
CDI-implementations.
---------------------------------------------------------------------------------
Key: CDI-113
URL:
https://issues.jboss.org/browse/CDI-113
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Alexey Kazakov
We need such metadata for tooling.
It would be very helpful to have some metadata for beans which implement spec required
services (BeanManager, ...)
Or for any other beans which CDI implementations register programmatically and which
should be available for users.
For example Weld loads some beans from jars which don't have beans.xml but some of
those beans are available for injections.
So far we don't have any documented way to recognize such beans.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira