https://issues.apache.org/bugzilla/show_bug.cgi?id=47834
--- Comment #9 from Guillaume Sauthier <[email protected]> 2009-09-15 04:38:01 PDT --- Just a note to remember how we discovered the problem. That may help to find the right solution, as my first bug explanation was not right. It's with TC6.0.20. In JOnAS we're deploying a development EAR, meaning an EAR unpacked (EjbJar unpacked and webapp unpacked, but lids in WEB-INF/lib still packed). There is a ClassLoader hierarchy: EjbJarsLoader (created by JOnAS and containing a "file://.../ejbjar.jar/" URL: unpacked form) parent of WebappClassLoader (created by Tomcat, untouched). In TC6, the TLDs where discovered only using the ClassLoader scan. So, when it was analyzing the unpacked EjbJar URL, it was failing because the code was expecting an regular jar file. In TC7, things are different: 1. TLDs declared in web.xml 2. TLDs found in WEB-INF/ and subdirectories (excluding WEB-INF/lib/ and WEB-INF/classes/) 3. TLDs from regular jar files discovered in WEB-INF/lib/ 4. ClassLoader scanning BTW, additionnal question, I see that the WEB-INF/classes directory will never be scanned for *.tld if the SCAN_CLASSPATH is not set. Is this a spec requirement (that TLD cannot be in WEB-INF/classes ) ? I say that because WEB-INF/classes can only be searched during the ClassLoader scanning, and then, it's failing because the code is expecting a regular file, not a directory.... -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
