My jsp pages (which contains Chinese characters and encoded in UTF8) can be executed without any problems in Tomcat 4.1 and Tomcat 5.0. When I try to run these jsp pages in Tomcat 5.5, either it will result in compile errors or the Chinese characters can not be displayed correctly on the browser. Then I tried to replace jasper-compiler.jar and jasper-runtime.jar in Tomcat 5.5 with those in Tomcat 5.0 and all back to normal.
Can you provide a test case ?
Created attachment 12737 [details] a simple jsp which contains a few chinese chars with UTF8 encoded
Created attachment 12739 [details] another jsp which will cause compile error
I can't test the correctness of the characters right now, but I do not get any compilation error with the second file. So this part of the report is bad. Although I'm not the biggest expert in i18n, one of the pages seem wrong: it does not include a page directive with the correct charset. Last, you might want to try using the init-param of Jasper (in conf/web.xml) to play with the encoding during the compilation. <init-param> <param-name>javaEncoding</param-name> <param-value>ISO-8859-1</param-value> </init-param>
Created attachment 12742 [details] test jsp on tomcat 5.0
Created attachment 12743 [details] test jsp on tomcat 5.5 with default javaEncoding
Created attachment 12744 [details] test jsp on tomcat 5.5 with javaEncoding set to ISO-8859-1
I tested the second jsp on three environment settings and got three different results(please see the attatched images): 1. on tomcat 5.0 with default jsp compiler setting: ok 2. on tomcat 5.5 with default jsp compiler setting: compile error 3. on tomcat 5.5 with javaEncoding set to ISO-8859-1: display incorrectly
The is not productive at all. As I said: the syntax error does not occur for me. So I will ignore this part of the report until I get a real test case. As for the rest, since the generated source will very likely be the same (you didn't compare, though), and the encoding is properly set on the compiler (you can verify that in the compiler adapter source), the issue must rest with the compiler itself. You have the option of using Ant as the compiler if JDT is the issue (remove the JDT jar, and put ant.jar where the JDT jar was). Supporting JDT is outside of Tomcat's scope, so I will resolve this report as INVALID.