[
https://jira.jboss.org/browse/WELD-662?page=com.atlassian.jira.plugin.sys...
]
Dan Allen commented on WELD-662:
--------------------------------
The issue is that Weld cannot read a package archived within a packaged archive because of
the path syntax it gets back from
ClassLoader#getResources("META-INF/beans.xml").
I've prepared an Arquillian test case in a standalone project. The project includes
three tests.
CDISmokeTest
EnterpriseArchiveContainingBeanArchiveTest
WebArchiveContainingBeanArchiveTest
The CDISmokeTest should run successfully on JBoss AS 5.1. The second two contain bean
archives (a jar containing beans.xml) which Weld will attempt to scan and fail, as
reported in this issue. If you clone and build my proposed branch for ARQ-315, you can set
the archive to be exploded upon deployment. In that case, the second two tests will pass,
since Weld is no longer having to access a packaged archive within a packaged archive.
To run the test, first start an instance of JBoss AS 5.1. Then, run the CDISmokeTest as
follows:
mvn test -Dtest=CDISmokeTest
After you get that working, then try one of the other two tests using a parallel command:
mvn test -Dtest=EnterpriseArchiveContainingBeanArchiveTest
You can stop JBoss AS 5.1 and start JBoss EAP 5.1, then run the tests there instead:
mvn test -Dtest=CDISmokeTest -Parq-jbosseap-remote
To see the test pass, you need to use Arquillian snapshot, built from the ARQ-315 proposed
branch:
mvn test -Dtest=EnterpriseArchiveContainingBeanArchiveTest -Parq-jbosseap-remote
-Dversion.arquillian=1.0.0-SNAPSHOT
weld-servlet-jboss5 can't scan jars nested in WEB-INF/lib
---------------------------------------------------------
Key: WELD-662
URL:
https://jira.jboss.org/browse/WELD-662
Project: Weld
Issue Type: Bug
Components: Servlet Container Support
Reporter: Pete Muir
Assignee: Ales Justin
Fix For: 1.1.0.Beta2
If you try deploying a non-exploded war to EAP 5.1 with weld-servlet-jboss5 with jars to
scan in WEB-INF/lib, the scanner fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira