anonymous wrote : So, I've run into this (in anger) as well now. | | 1) Facelets scans the classpath for .taglib.xml files inside of META-INF, and loads them if it finds them (thats what all the load implicit stuff you see is). | | 2) The UCL doesn't scan WEB-INF/lib (as this is a special war thing). | | So, if you get the UCL instead of the WebAppClassLoader then it don't work. And, I found that even if the classloader inside FaceletsRenderer is the WACL then the UCL may be used to initialise facelets. | Yeah - I looked at the facelets source code - by hacking it to show the classloader, that's where I ultimately discovered that two different classloaders are being used (but I still don't know why this occurs - I could understand if the UCL is always being used and thus usage always fails - but not why sometimes the WACL is being used???). Anyway, now we come to why I suggested maybe putting a hack on facelets to try and force it to use the WACL only by using the ServletContext's classloader .... any thoughts? Thanks, Brad Smith View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022418#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...