[ http://jira.jboss.com/jira/browse/RF-2914?page=comments#action_12419026 ] Marian FILLO commented on RF-2914: ----------------------------------
I have the same warning message in log after trying out the first JBoss Rich Faces example from chapter 3.3. Simple Ajax Echo Project of JBoss Rich Faces User Guide. Every time an AJAX call is processed by the server (which is after every key pressed within the sample text input line) a warning appears in the log. Every postback adds also a warning into log, every page redirect adds two. After commenting-out the RichFaces filter from web.xml, problem disappears (but RichFaces pages dont work, of course). So the conclusion is - every time a request comes into RichFaces filter, warning appears in the log. I am using JBoss Rich Faces 3.2.1, JSF 1.2, Facelets 1.1.14, GlassFish appserver from JavaEE SDK 5 bundle Update 5. Application works fine, even with international characters. I think this bug is easily reproducible and thus should be fixed soon. The problem should be somewhere very soon after receiving request, because pages with no Rich Faces / Ajax4JSF tags also add a warning to log. Hopefully there is a redundant encoding setting which could be deleted, or non-redundant one which should be moved several lines up (before reading first request parameter). So good luck to coders and hope to see the fix in the next release (3.2.2?). > Error starting RichFaces enabled web application after switch to 3.2.0 release > ------------------------------------------------------------------------------ > > Key: RF-2914 > URL: http://jira.jboss.com/jira/browse/RF-2914 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.0 > Environment: jsf 1.2_08, glassfish 9.1 > Reporter: Mareks Malnacs > Assigned To: Nick Belaevski > Priority: Minor > Fix For: Future > > > Complex richfaces application works fine with 3.1.4 release. After update > project libraries to 3.2.0 glassfish displays following message in error log: > PWC4011: Unable to set request character encoding to UTF-8 from context > /proc, because request parameters have already been read, or > ServletRequest.getReader() has already been called > and firefox displays empty page. > If I switch back to 3.1.4 - application works fine. > Any changes in web.xml (or any other web-app configuration file) I am missed > during "upgrade" ? > Thanks, > Mareks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ richfaces-issues mailing list [email protected] https://lists.jboss.org/mailman/listinfo/richfaces-issues
