[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...
]
Alexey Kazakov commented on CDI-113:
------------------------------------
> However, these cases are well specified.
They are well
specified for runtime but not for tools.
How should tools recognize BeanManager implementations? What if there are a few classes
that implement this interface? Only particular CDI container knows what to load to provide
spec required services.
And one more problem. CDI container don't have to look in jars without beans.xml at
all. So no beans.xml no any need to scan such jars. But for tools it's not the case.
Tools have to look in all the jars in class path if they want to find all BeanManager
implementations. Otherwise they need to know all the available CDI-implementations to work
around this problem using hard-coded names/paths.
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