[cdi-dev] [JBoss JIRA] Commented: (CDI-113) Add some design time readable metadata for built-in beans of CDI-implementations.
[
https://issues.jboss.org/browse/CDI-113?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on CDI-113:
-------------------------------
I don't think that Weld loads any beans from jars which don't have beans.xml. Any
built-in bean that Weld provides is clearly documented in the CDI specification. Examples
include BeanManager, UserTransaction and a few others (security principle, validation
factory). Some may depend on the runtime environment (such as when Weld runs in a Servlet
environment). However, these cases are well specified.
It's accurate to say that extensions can load beans from jars which don't have
beans.xml. The most basic example is using the BeforeBeanDiscovery#addAnnotatedType() in
an extension method that observes this event. It's those cases when metadata is
probably useful. Granted, this would have been possible had the XML configuration schema
been approved. So perhaps the right approach is to pursue that request.
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