Thanks Mikolaj. That did it.
For some reason running request.setCharacterEncoding("UTF-8") in my code
does nothing, but if it gets run from a Filter it works great.
Tim Koop
Mikolaj Rydzewski wrote:
Tim Koop wrote:
I have a web page form that is expecting UTF-8 data, but wh
eb site on your
server. If you have more that one instance of Tomcat running maybe you
restarted the wrong one. Check file permissions. Maybe the new class
is actually running and the changes you made to the java file don't
actually fix the problem.
Tim Koop
none none wrote:
Hello,
I a
l is actually
sticking? I couldn't find any errors in localhost.log nor in
cataline.out (well, no relavent errors at least).
Thanks a lot, to anyone who has any ideas.
--
Tim Koop
Mark Thomas wrote:
1. Try accessing Tomcat directly to see if mod_jk is causing problems.
2. Try 4.
for (int i=0; i
<% } %>
2. Maybe you are producing the xml/jsp on a Windows computer that
produces CR + LF characters and viewing it on a computer that interprets
these as two separate EOL characters. This is not as likely as number 1
above.
Tim Koop
Kiran Patel wrote:
Hello all,
I
Sun JVM 1.4.2, Linux
Fedora Core 2.4.22
A part of my server.xml file looks like this:
protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler"
URIEncoding="UTF-8"
useBodyEncodingForURI="false" />
Thanks for any ideas. I've tried ev
In case you're curious, I tried it with Sun's Java SDK 1.4.1 and all works
fine.
Tim Koop
www.timkoop.com
- Original Message -----
From: "Tim Koop" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 23, 2002 4:08 PM
Subject: JVM crashes w
