Which version is this?
For a while it looked like the standards were moving URLs
towards using UTF8. Jetty probably jumped a little early
and we have sinced switched back. I'm sure if you
update to the latest Jetty (4.1.0) or a recent JBoss (eg 3.2.0b) then you will not have this problem.
You can read about this at:
I just have another way to workaround without transforming the properties files:
Jetty: <%@ page contentType='text/html;charset=UTF-8' %>
Tomcat: <%@ page contentType='text/html' pageEncoding='UTF-8' %>
Adding these directives to every page can solve the problem. It is strange that using the Tomcat's directive to Jetty or Jetty's directive to Tomcat will display '?' for non ascii characters in the browser.