]
Geoffrey De Smet updated SOLDER-220:
------------------------------------
Comment: was deleted
(was: Replicated again today with weld 1.1.2.Final and seam 3.1.0.Beta3 on GWT-hosted
model (= Jetty 6 with some tomcat stuff).
Note that the WEB-INF/classes/META-INF/beans.xml workaround is NOT compatible with JBoss
AS 7 which requires it to be WEB-INF/beans.xml ...)
Seam-config ignores WEB-INF/beans.xml (and WEB-INF/seam-beans.xml) in
tomcat 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
Assignee: Stuart Douglas
Priority: Critical
Probably does work in AS 6/7, but not in Tomcat 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 returnts 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: