FYI
> [EMAIL PROTECTED] wrote:
>> Well, i rechecked all twice, i't a new fresh install.
>> The only old thing is the app context, that is not embedded into server.xml
>> but as a standalone file.
>> I still had a doubt about the jk module that was compiled for 4.1.10, but i
>> downloaded 4.1
There is still a bug in Jasper 2 (tomcat 4.1.10) that generates incorrect
code for IterationTag (s). There is no variable synchronization between
doStartTag() and the loop body.
The following (snippet) of a jsp page with an IterationTag ...
--- ---
I can count to ten.
could be due to this bug...
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11552
This has been fixed but I am not sure if the
fix has been applied to the tomcat 4 branch yet.
> -Original Message-
> From: Dev Zero G Ltd team [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 27, 2
t say to commiter
> to fix the problem.
>
> pageEncoding is assessment of JSP specification 1.2 and
> Tomcat shuold be
> take a leaf of specification.
>
> Is this "Tomcat Develepers List" is not suit for this kind of
> opinion???
>
>
> - Original M
I found that if you don't specify the language attribute then encoding seems
to
be ignored.
example:
<%@ page contentType="text/html; charset=Shift_JIS" pageEncoding="Shift_JIS"
%>
Does NOT work (UFT8 is assumed) but...
<%@ page language="java" contentType="text/html; charset=Shift_JIS"
pageE
a release soon.
Thanks to everyone for their efforts on Tomcat !
-Original Message-----
From: David Shanahan
Sent: Monday, August 12, 2002 3:54 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [4.1.9] New test milestone released
There is a bug in 4.1.9 (a Jasper bug) that breaks my
ap
There is a bug in 4.1.9 (a Jasper bug) that breaks my
application completely.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11552
We use custom tags that do iteration (they implement IterationTag)
but do not modify their content so they do not implement BodyTag.
The latest versions of Jasp
I have been trying out 4.1.0. I have noticed that if you
do not specify the language attribute in the page directive
then the contentType attribute has no effect on the page encoding.
If I do this:
<%@ page contentType="text/html; charset=Shift_JIS" %>
and then look at generated source code f
> if (cookies[i].getName().equals("memberCookie")); {
It looks like the problem is the semicolon after the "if()" ^
This code will print out all the cookies, not just the "memberCookie".
- Original Message -
From: "Paul Wallace" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMA
