Weld SE should support modular bean declaration archives, and bean sharing
--------------------------------------------------------------------------
Key: WELD-959
URL: https://issues.jboss.org/browse/WELD-959
Project: Weld
Issue Type: Feature Request
Components: Java SE Support
Affects Versions: 1.1.2.Final
Environment: JBoss Modules 1.0.1.Final
Reporter: Lincoln Baxter III
When booting weld SE in a modular environment (JBoss Modules), it currently
takes the TCCL and scans all beans it can find; however, there is no concept of
a modular structure between these beans. Take Forge, for instance:
Forge (A beans archive) bundles Seam Render, a templating library, for use in
rendering various types of output. Seam Render is also a Beans Archive.
When a forge Plugin (also a Beans archive) includes Seam Render, now there is a
conflict. What *should* happen, is that Weld uses Seam Render beans from the
archive bundled with Forge's modules, for forge, and uses the Render beans
bundled in the plugin's modules, for the plugin. What actually happens is that
weld throws an "Unsatisfied injection point" exception.
If the plugin is compiled against the Seam Render JAR, but does not bundle it
(provided scope,) then a ClassNotFoundException is thrown.
It should be possible to share beans across modules properly in Weld SE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
