[
https://issues.jboss.org/browse/SOLDER-220?page=com.atlassian.jira.plugin...
]
Geoffrey De Smet commented on SOLDER-220:
-----------------------------------------
Upgraded to solder + seam 3.1.0.Beta4 (yes, I verified the solder version is correct
despite the bom problem).
The entire issues is masked by regression SEAMSECURITY-121 in that case.
Seam-config ignores WEB-INF/beans.xml (and WEB-INF/seam-beans.xml) in
jboss 7 and tomcat 6 for seam-config configuration (but not weld configuration)
-----------------------------------------------------------------------------------------------------------------------------------------------------
Key: SOLDER-220
URL:
https://issues.jboss.org/browse/SOLDER-220
Project: Seam Solder
Issue Type: Bug
Affects Versions: 3.0.0.Final
Environment: Tomcat 6, linux, IntelliJ
Reporter: Geoffrey De Smet
Priority: Critical
Does not work in jboss 7, tomcat 6 and gwt hosted mode (~ jetty 6).
Occurs for both exploded war and not exploded war.
Strangely enough, it doesn't ignore it for the root xml schema validation.
The problem is probably in ClasspathResourceLoader.getResources(String name):
when name = "WEB-INF/beans.xml", it returns an empty Set, while it should
contain something like:
/.../guvnor/guvnor-webapp/target/guvnor-webapp-5.3.0-SNAPSHOT/WEB-INF/beans.xml
Thread.currentThread().getContextClassLoader() returns an instance of
org.apache.catalina.loader.WebappClassLoader
When asking
Thread.currentThread().getContextClassLoader().getResourceAsStream("WEB-INF/beans.xml")
or
Thread.currentThread().getContextClassLoader().getResourceAsStream("/WEB-INF/beans.xml")
it returns null (so the catalina WebappClassLoader returns null for that).
even this returns null:
or
Thread.currentThread().getContextClassLoader().getResourceAsStream("WEB-INF/web.xml")
yet asking a resource, such as
Thread.currentThread().getContextClassLoader().getResourceAsStream("/drools-asseteditors.xml")
does not return null, but the correct resource.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira