[
https://issues.jboss.org/browse/CDI-113?page=com.atlassian.jira.plugin.sy...
]
Alexey Kazakov commented on CDI-113:
------------------------------------
Ok. If it is not interesting to look at particular implementation of built-in beans at all
and having navigation to the interfaces only is enough then JBT doesn't need any
additional metadata. Actually JBT already works in this way - JBIDE-8697.
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
Affects Versions: 1.0
Reporter: Alexey Kazakov
Fix For: TBD
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