[
https://issues.jboss.org/browse/CDI-113?page=com.atlassian.jira.plugin.sy...
]
Pete Muir commented on CDI-113:
-------------------------------
I would say it's actively wrong to have the tool look at the impl of a built in bean,
or to navigate to them. Part of the goal of a specification is to encourage people to
write portable code, encouraging them to look at implementations is not a good way to do
this!
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