[
https://issues.jboss.org/browse/CDI-87?page=com.atlassian.jira.plugin.sys...
]
Geoffrey De Smet commented on CDI-87:
-------------------------------------
Presume this embedding scenario:
Project A does not use weld or CDI directly. It depends on B and C.
Project B has CDI and weld use as optional: it does not use weld by default, but includes
a beans.xml in it's classpath in case you want to take advantage of that
Project C uses CDI and weld. It doesn't depend on B. It knows nothing of B (so it
wouldn't presume excluding it). It has no intention of being any influence on anything
B related.
Result: Because C fires up weld, which as a side-effect fires up the beans.xml of B. That
shouldn't happen.
Declarative control over classes including in bean archive scanning
-------------------------------------------------------------------
Key: CDI-87
URL:
https://issues.jboss.org/browse/CDI-87
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Packaging and Deployment
Affects Versions: 1.0
Reporter: Pete Muir
Fix For: 1.1 (Proposed)
Weld introduced a XML syntax for this
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira