Tomcat is open source. You should be able to get the archived source
for any version and apply the fix that is making 3.3 work. I would scan
bugzilla for your error and then see if CVS has a patch around that
time. That seems shortsighted when you could upgrade to a recent version
of Tomcat that will perform better, support the latest standards, and is
working on hundreds of other iSeries systems. I have migrated dozens of
Tomcat servers/applications from 3.2.x to 4.x and have run into only
minor problems that were relatively easy to fix. With a recent version
if you found this problem it would likely be fixed very quickly with a
post to the Tomcat developers list.

David Morris

>>> JustD@xxxxxxxxxxxxxxxx 9/22/2004 2:55:56 PM >>>


      I have a web application that is supposed to take in UTF-8
off a HTML Form.
It is running on Tomcat 3.2.4 with Java 1.3 on the iSeries.
The problem is that when non-english characters are input into the
they are encoded incorrectly on the submit.
 When the code tries to decode the parameter it comes back garbage.
>From my research I discovered that if you specify <DecodeInterceptor
defaultEncoding="UTF-8" />
in the server.xml file tomcat should use the specified encoding for
This solution works wonderfully when i run the application on my local
windows tomcat server (3.3),
but when i move the application to the iSeries it still fails.

I've also tried setting the default encoding to UTF-8 in my Apache
and tried Tomcat running both in and out of process.   Nothing works.
Anybody have any suggestions?

Moving to newer version of tomcat is not an option, nor can I upgrade
version of Java.

David Just

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.