Kalle,
I tried what you did, and it seems
to suppress the caracter encoding complaint, but there still remains the content
type.
And
you cannot set the content type anywhere in ServletRequest or
HttpServletRequest.
Does
anyone else have this problem ?
Mark
De : Korhonen, Kalle [mailto:[EMAIL PROTECTED]
Envoy� : mercredi 17 novembre 2004 10:37
� : MyFaces Discussion
Objet : RE: Why does HtmlResponseWriterImpl keep complaining ?I would think that it is because JSF lifecycle has already started and it check the headers before page parsing has started. If you set them yourself in the filter, you can suppress the errors. We did it for character encoding and didn't worry about setting the content type at all just yet.Kalle
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 17, 2004 5:20 AM
To: [EMAIL PROTECTED]
Subject: Why does HtmlResponseWriterImpl keep complaining ?Anyone know why I constantly get the following information logged to my console when executing a JSF app ?
[04-11-17 08:12:45:859 EST] 5c005c HtmlRenderKit I net.sourceforge.myfaces.renderkit.html.HtmlRenderKitImpl No content type list given, creating HtmlResponseWriterImpl with default content type.
[04-11-17 08:12:45:869 EST] 5c005c HtmlResponseW I net.sourceforge.myfaces.renderkit.html.HtmlResponseWriterImpl No content type given, using default content type text/html[04-11-17 08:12:45:869 EST] 5c005c HtmlResponseW I net.sourceforge.myfaces.renderkit.html.HtmlResponseWriterImpl No character encoding given, using default character encoding ISO-8859-1
This is in the header of each of my JSP pages:
<
head><meta http-equiv="content-type" content="text/html; charset=iso-8859-1"></head>
Thanks in advance,
Mark
