No filters, but as it turns out, the problem appears to be JSF acting
differently when deployed to Resin than when deployed to another app server
(SJSAS in this case).
For JSF to keep the encoding intact required explicitly setting the content
type in the JSP to utf-8 using a page directive. Not sure why Sun's application
server behaves differently, but that's another story, and the problem is solved.
From: Scott Ferguson [mailto:[EMAIL PROTECTED]
Sent: Monday, October 09, 2006 10:58 AM
To: Michael Stevens
Subject: Re: [Resin-interest] Unicode characters supplanted by HTML 4.0 entity
On Oct 9, 2006, at 10:58 AM, Michael Stevens wrote:
> I am seeing behavior in Resin where unicode characters are being
> replaced by HTML entity references in the page response.
Can you check for any filters? Resin doesn't automatically escape anything.
The only processing Resin does is for PrintWriter (e.g. JSP) converting 16-bit
chars to 8-bit binary.
resin-interest mailing list