[
https://issues.jboss.org/browse/ARQ-279?page=com.atlassian.jira.plugin.sy...
]
Dan Allen edited comment on ARQ-279 at 3/3/11 7:25 PM:
-------------------------------------------------------
This causes a lot of problems in testing Seam modules that use Solder. The tests work fine
when run against a real container (like JBoss AS 6 remote), but then fail when using Weld
EE embedded. The reason, as you mentioned, is because the embedded container ignores bean
archive libraries (in WEB-INF/lib for example)
The workaround is to include the bits that you need from the bean archive library into the
main classpath of the test archive, but that really makes for some ugly looking tests.
was (Author: dan.j.allen):
This causes a lot of problems in testing Seam modules that use Solder. The tests work
fine when run against a real container (like JBoss AS 6 remote), but then fail when using
Weld EE embedded. The reason, as you mentioned, it because the embedded container ignores
bean archive libraries.
The workaround is to include the bits that you need from the bean archive library into the
main classpath of the test archive, but that really makes for some ugly looking tests.
Weld SE should support nested Jars
----------------------------------
Key: ARQ-279
URL:
https://issues.jboss.org/browse/ARQ-279
Project: Arquillian
Issue Type: Feature Request
Components: Weld Containers
Reporter: Aslak Knutsen
Fix For: 1.0.0.Beta1
In any larger app, Libraries are needed. Weld SE container should support the notion of
Nested JavaArchives in the @Deployment.
Should work about the same as for Weld EE, scan through the Archives recursively looking
for class/beans.xml/extensions etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira