tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 11739] New: - Unable to locate TLDs based on <uri> element
Date Thu, 15 Aug 2002 19:08:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11739>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11739

Unable to locate TLDs based on <uri> element

           Summary: Unable to locate TLDs based on <uri> element
           Product: Tomcat 5
           Version: Nightly Build
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jasper2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: prasad.subramanian@sun.com


In Jasper2 from Tomcat 4.17 onwards if a TLD is defined with an <uri> element
and this uri is used to access the TLD in the jsp , the container is uanble to
create a mapping for it.

Case I:
<uri>element in the TLD  is  /MyTaglib
uri attribute in the taglib directive is /MyTaglib

TLD is physically located in WEB-INF/tlds

Result: Exce[ption saying file /MyTaglib not found

Case II:
<uri> element in the TL D is an absolute URI
uri attribute in the taglib direcxtive is the smae absolute uri
TLD is physically present in WEB-INF/tlds

results: Exception saying the the abolute URI could not be found in the web.xml
or any of the jars deployed with the app.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message