Gavin - this is a bug in Seam.  The current Seam code just happens to work.  
The WAR classloader does not contain the entire WAR file.  It only contains 
WEB-INF/classses and WEB-INF/lib/*.jar.  When you read "/WEB-INF/pages.xml" 
from the WAR classloader, you are actually getting it from the parent 
classloader (the EAR classloader) which *DOES* include the WAR file contents in 
the classpath.  (And I don't think this is required by the spec.  I think this 
is just the way JBoss happens to work, but I could be wrong on that point)

When you have two WAR files in the EAR and try to read pages.xml, no matter 
which WAR classloader is the context classloader, it goes to the EAR 
classloader in both cases.  If the pages.xml is in both WARs, it's a toss up 
which one you get.  But, you'll get the same one from both apps.

This is a case where you definitely need to go to the ServletContext (going 
through FacesContext, as rdewell suggests is fine) so that you can read the 
file correctly out of the WAR.  

I think moving the FacesContext to the front of the list of places to check in 
util.Resources makes sense to me since there doesn't appear to be any way to 
NOT put the WAR file directly on the EAR classloader.  (I don't understand why 
we do that though - it makes no sense and it has caused problems in HAR 
deployer too)

View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3940345#3940345

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3940345


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to