Bug 14200 - TLDs under WEB-INF are not scanned for URI mappings
Summary: TLDs under WEB-INF are not scanned for URI mappings
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 4
Classification: Unclassified
Component: Jasper 2 (show other bugs)
Version: 4.1.14
Hardware: All All
: P3 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
: 11739 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-11-03 02:37 UTC by Hans Bergsten
Modified: 2004-11-16 19:05 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Hans Bergsten 2002-11-03 02:37:27 UTC 
Even though the JSP 1.2 spec is a bit vague on the subject, I'm pretty sure the
intention is that the auto-discovery of TLDs includes TLDs located directly in
the file system under WEB-INF, but the
org.apache.jasper.compiler.TldLocationsCache class only looks for TLDs in JAR
files under WEB-INF/lib. 

For consistency with which TLDs are used when scanning for listeners, I suggest
including all TLDs under WEB-INF (in addition to JAR files under WEB-INF/lib and
web.xml mappings) when the map is created.

I'll try to get this clarified in JSR-152.
Comment 1 Hans Bergsten 2003-01-28 06:46:27 UTC 
Looks like this one only got fixed for TC 5. I'd appreciate it if someone can
port it to TC 4.1 as well (it doesn't work in TC 4.1.18, have not tested 4.1.19
yet).

It's been clarified by JSR-152 that the auto-discovery of TLDs includes TLDs
located directly in the file system under WEB-INF (for JSP 2.0, but there's no
reason not to do the same for JSP 1.2).
Comment 2 Jan Luehe 2003-02-07 23:34:37 UTC 
I did port the changes back to TC 4.1, but they were not picked up by TC 4.1.18.
They have been picked up by TC 4.1.19, though.
Comment 3 Jan Luehe 2003-02-28 23:03:36 UTC 
*** Bug 11739 has been marked as a duplicate of this bug. ***