myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott O'Bryan (Commented) (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Commented] (TRINIDAD-2095) Mojara and PWC4011: Unable to set request character encoding to UTF-8
Date Tue, 20 Mar 2012 15:21:39 GMT

    [ https://issues.apache.org/jira/browse/TRINIDAD-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233478#comment-13233478
] 

Scott O'Bryan commented on TRINIDAD-2095:
-----------------------------------------

Thomas, I don't see this happening in the general case and I don't think that the issue is
as you say.  I find it more likely that something in the filter chain is causing a getWriter()
to be executed while some other piece of software (toplink?) tries to set the character encoding
without checking to see if the response has been committed.  Bottom line is, the character
encoding cannot be set on a committed response as per J2EE.

Before we can even HOPE to make progress on this, we'll need a test case and "maybe" we can
either defer the call to getWriter() in the filterchain or suggest that you file a bug against
the framework that is trying to set this on a committed response.
                
> Mojara and PWC4011: Unable to set request character encoding to UTF-8
> ---------------------------------------------------------------------
>
>                 Key: TRINIDAD-2095
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2095
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions: 1.2.14-core 
>            Reporter: Tomas Havelka
>            Priority: Minor
>
> The problem with annoying warning message with Mojarra and Glassfish still remains.
> Within each request TrinidadFilterImpl creates the ServletExternalContext multiple times
which causes Mojarra to log this message "PWC4011: Unable to set request character encoding
to UTF-8" many many times (cca 4x per request). This causes the log file is getting large
unreasonably. The problem is descibed in this thread http://www.mail-archive.com/dev@myfaces.apache.org/msg37786.html.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message