Bug 16535 - Using fmt taglib (ver 1.0.2) with Tomcat 4.1.18
Summary: Using fmt taglib (ver 1.0.2) with Tomcat 4.1.18
Alias: None
Product: Taglibs
Classification: Unclassified
Component: Standard Taglib (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2003-01-29 10:22 UTC by Eric Tan
Modified: 2004-11-16 19:05 UTC (History)
0 users

war file that reproduces the jstl 1.0.2 fmt resourcing issue with tomcat 4.1.18 (case 16535) (464.38 KB, application/octet-stream)
2003-02-04 04:14 UTC, Eric Tan

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Tan 2003-01-29 10:22:49 UTC
When using the JSTL (ver 1.0.2) fmt taglib with tomcat 4.1.2 (the tomcat that
comes with Java Web Services DevKit), everything works nicely. However, when I
switched to tomcat 4.1.18, only the very first resource message is displayed
correctly while subsequent calls to fmt:message shows ????key2????.

My browser is Netscape 7.0.1.

My code segment is as follows:

<title>Test JSP</title>

<%@ taglib uri="/jstl-fmt" prefix="fmt" %>

<fmt:bundle basename="resources.DisplayMessages">
  <fmt:message key="key1"/>
  <fmt:message key="key2"/>
  <fmt:message key="key3"/>


On tomcat 4.1.2, output is:

On tomcat 4.1.18, output is:

If I do another request to this jsp page, on tomcat 4.1.18, all output becomes

I'm using the same war file for both tomcat versions and the resource file,
DisplayMessages.properties, is located in the WEB-INF/classes/resources directory.
Comment 1 Pierre Delisle 2003-01-30 20:27:04 UTC
I tested with JSTL 1.0.2/Tomcat 4.1.18, and it worked for me.
If you still have a problem after checking your setup,
could you attach the simplest war possible that 
triggers the problem, and I'll test with that.
Comment 2 Eric Tan 2003-02-04 04:14:44 UTC
Created attachment 4707 [details]
war file that reproduces the jstl 1.0.2 fmt resourcing issue with tomcat 4.1.18 (case 16535)
Comment 3 Eric Tan 2003-02-04 04:26:25 UTC
Attached a simple war file that reproduces this problem.

After deploying, use http://host:port/jstlfmttest/testjsp to access the test case.

I am using tomcat 4.1.18 right after installation without any changes to the

If I switched to using 

<fmt:setBundle basename="resources.DisplayMessages"/> 

instead of 

<fmt:bundle basename="resources.DisplayMessages" prefix="test.">

,I can get the jsp to work for both tomcat 4.1.2 and 4.1.18.


Comment 4 Pierre Delisle 2003-02-05 00:52:04 UTC
Thanks for the attachment Eric. Indeed, I could reproduce the bug.
The good news though is that this bug has already been taken care of
when we fixed bug 14695. If you use the nightly build of JSTL, everything
should work fine.