Bug report #569 has just been filed.

You can view the report at the following URL:

   <http://znutar.cortexity.com/BugRatViewer/ShowReport/569>

REPORT #569 Details.

Project: Tomcat
Category: Bug Report
SubCategory: New Bug Report
Class: swbug
State: received
Priority: low
Severity: non-critical
Confidence: public
Environment: 
   Release: 3.2
   JVM Release: 1.3
   Operating System: Windows NT
   OS Release: 4.0 sp6a
   Platform: Intel

Synopsis: 
Tag libraries not found

Description:
I'm using a tag library that is included using the uri "/uiTags". With Tomcat 3.1 it 
works nicely. It also worked with an early beta of 3.2. However, Tomcat 3.2 fails with 
an error and complains that it can't find the file "...\myApplication\uiTags".

If I copy the tag library descriptor from WEB-INF/jsp/ui-taglibs.tld to the document 
root and renames it to uiTags everything works!

It appears that the taglib tag ín web.xml is ignored somehow. As it works with 3.1 
(and Orion) I think that the web.xml file is correct.
Title: BugRat Report # 569

BugRat Report # 569

Project: Tomcat Release: 3.2
Category: Bug Report SubCategory: New Bug Report
Class: swbug State: received
Priority: low Severity: non-critical
Confidence: public

Submitter: _Anonymous ( [EMAIL PROTECTED] )
Date Submitted: Dec 12 2000, 06:35:35 CST
Responsible: Z_Tomcat Alias ( [EMAIL PROTECTED] )

Synopsis:
Tag libraries not found
Environment: (jvm, os, osrel, platform)
1.3, Windows NT, 4.0 sp6a, Intel

Additional Environment Description:

Report Description:
I'm using a tag library that is included using the uri "/uiTags". With Tomcat 3.1 it works nicely. It also worked with an early beta of 3.2. However, Tomcat 3.2 fails with an error and complains that it can't find the file "...\myApplication\uiTags". If I copy the tag library descriptor from WEB-INF/jsp/ui-taglibs.tld to the document root and renames it to uiTags everything works! It appears that the taglib tag ín web.xml is ignored somehow. As it works with 3.1 (and Orion) I think that the web.xml file is correct.

Workaround:
null

View this report online...

Reply via email to