[WICKET-1816] Wicket 1.3.4 violates servlet standard, Glassfish spews warnings

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.4
• Fix Version/s: 1.3.5, 1.4-RC1
• Component/s: wicket
• Assignee: Igor Vaynberg
• Reporter: Gili
• Created: 02/Sep/08 05:44
• Updated: 19/Jul/11 07:14
• Resolved: 27/Sep/08 04:12

Description

WicketFilter.java line 194 invokes getLastModified() which invokes "request.getParameterMap()" on line 962. Later on in that same request, WicketFilter.java line 222 invokes doGet() which invokes response.setCharacterEncoding() on line 376.

This is just one case where this problem occurs but I believe others might exist. Whenever Wicket violates the standard Glassfish spews out this warning:

PWC4011: Unable to set request character encoding to UTF-8 from context <context-path>, because request parameters have already been read, or ServletRequest.getReader() has already been called

... you literally end up with tens of these warnings per request, and supposedly, the wrong behavior Glassfish's FAQ discusses this in more detail: http://wiki.glassfish.java.net/Wiki.jsp?page=FaqWebAppUnableToSetRequestCharEncoding

Issue Links

• is duplicated by: WICKET-3908 Encoding problem with POSTing a form with Ajax