Nope, I'm not using a servlet to load the jsp resource.
-----Original Message-----
From: Edmund Lai [SMTP:[EMAIL PROTECTED]]
Sent: Sunday, May 27, 2001 6:44 PM
To: [EMAIL PROTECTED]
Subject: Re: Issues with Tomcat 3.2.1, JSPs and I18N ( Implicit character tran slation ??? )
Are you using a servlet to load the jsp resource by
using a RequestDispatcher.include()? If so, setting
content-type in the page directive should have no
effect. This is an excerpt from the Servlet 2.2 API
doc
"The included servlet cannot change the response
status code or set headers; any attempt to make a
change is ignored."
--
Ed
> A couple of other factors
> 1. Yes I'm setting the contentType to "text/html;
> charset=UTF-8" in the
> Page Directiive
> 2. Yes the browser is set to use the UTF-8
> encoding.
> 2. Yes I realize that the jsps are compiled into a
> servlet but while
> looking at the jsp compiled java src file
> it appears that the servlet uses a specialized
> class JspWriter to
> handle printing to the output stream.
> 3. ECS had a similar issue in previous versions.
> There are some tricky
> issues with how streams are handled
> so that you don't run into implicit and screwy
> character encoding
> issues.
>
> I would appreciate any feedback, I'm going to dig
> through the Tomcat source
> to see if I can find the root problem
> and would hate to do that if there was an easy
> answer that I'm missing.
>
> Thanks.
> Chris Halverson
>
> Christopher R. Halverson
> nCube
> [EMAIL PROTECTED]
> "Never underestimate the ability of any human to
> delude themselves,"
> "and convince others their delusion is absolute"
>
>
>
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
