[ http://jira.jboss.com/jira/browse/RF-2914?page=comments#action_12406172 ] Alexander Belov commented on RF-2914: ------------------------------------- Have the same message in server.log, application works. -- 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

[ http://jira.jboss.com/jira/browse/RF-2914?page=all ] Nick Belaevski updated RF-2914: ------------------------------- Fix Version/s: 3.2.1 Assignee: Vladislav Baranov -- 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

[ http://jira.jboss.com/jira/browse/RF-2914?page=comments#action_12408026 ] Matija Mazi commented on RF-2914: --------------------------------- I have the same (or similar) problem. I'm using JBoss Application Server 4.2.2 and Seam 2.0.1.GA. With RF 3.2.0 any international characters in forms are interpreted by the server incorrectly. I get two strange characters instead of one interantional; it seems the reqest is encoded in UTF-8 (as I want it to be) but the server interprets it as in some 8-bit encoding. The problem arises with RF 3.2.0, but not RF 3.1.4 (with no other changes in application except RF version). I don't get any nice error message as the one mentioned under in PWC4011 above, but already before reading this I suspected that something like that could be the reason (some part of the code reading request parameters before the request encoding is explicitly set on the server). I think this is a critical issue since it breaks normal functionality of any web application that requires (or is supposed to accept) any text input other than English! -- 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

[ http://jira.jboss.com/jira/browse/RF-2914?page=comments#action_12408032 ] Vladislav Baranov commented on RF-2914: --------------------------------------- The problem with international characters when using RichFaces 3.2.0 has been solved in the related issue RF-2962 and will be available in RF 3.2.0 SR1. The current issue is related to the warnings in the glassfish log, which seem not to break the functionality of the application. -- 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

[ http://jira.jboss.com/jira/browse/RF-2914?page=all ] Nick Belaevski updated RF-2914: ------------------------------- Assignee: Nick Belaevski (was: Vladislav Baranov) -- 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

[ http://jira.jboss.com/jira/browse/RF-2914?page=comments#action_12417620 ] Mike Hanafey commented on RF-2914: ---------------------------------- Tracing what leads up to the logged message reveals the following (in order of execution): org.ajax4jsf.webapp.BaseFilter: protected void processUploadsAndHandleRequest(HttpServletRequest request, HttpServletResponse response, FilterChain chain) throws IOException, ServletException { HttpServletRequest httpRequest = (HttpServletRequest) request; String uid = httpRequest.getParameter(UPLOAD_FILES_ID); In Glassfish, getParameter calls the following: org.apache.coyote.tomcat5.CoyoteRequest protected void parseRequestParameters() { /* SJSAS 4936855 requestParametersParsed = true; */ Parameters parameters = coyoteRequest.getParameters(); // getCharacterEncoding() may have been overridden to search for // hidden form field containing request encoding String enc = getCharacterEncoding(); // START SJSAS 4936855 // Delay updating requestParametersParsed to TRUE until // after getCharacterEncoding() has been called, because // getCharacterEncoding() may cause setCharacterEncoding() to be // called, and the latter will ignore the specified encoding if // requestParametersParsed is TRUE requestParametersParsed = true; During the restore view phase, when initView(FacesContext ) is called the following is called (in the same CoyoteRequest class), and because "requestParametersParsed" was set true above, the warning is logged. public void setCharacterEncoding(String enc) throws UnsupportedEncodingException { // START SJSAS 4936855 if (requestParametersParsed || usingReader) { String contextName = (getContext() != null ? getContext().getName() : "UNKNOWN"); log.warn(sm.getString("coyoteRequest.setCharacterEncoding.ise", enc, contextName)); return; } // END SJSAS 4936855 -- 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

[ https://jira.jboss.org/jira/browse/RF-2914?page=com.atlassian.jira.plugin... ] Kem Elbrader commented on RF-2914: ---------------------------------- Here is a workaround. Go to admin console (http://localhost:4848/) Go to Application Server -> Logging -> Log Levels Add a property with name org.apache.coyote.tomcat5.CoyoteRequest and value SEVERE Note: this will suppress other possibly important WARNING and INFO messages from CoyoteRequest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/RF-2914?page=com.atlassian.jira.plugin... ] Nick Belaevski resolved RF-2914. -------------------------------- Resolution: Done Assignee: Tsikhon Kuprevich (was: Nick Belaevski) 2QA team: Affected: 1. File upload 2. International GET parameters handling - e.g. conversation ids/query parameters -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira