[
https://issues.apache.org/jira/browse/WICKET-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gili closed WICKET-1816.
------------------------
I verified Johan's fix. It seems to solve the problem on my end.
> Wicket 1.3.4 violates servlet standard, Glassfish spews warnings
> ----------------------------------------------------------------
>
> Key: WICKET-1816
> URL: https://issues.apache.org/jira/browse/WICKET-1816
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.4
> Reporter: Gili
> Assignee: Igor Vaynberg
> Fix For: 1.3.5, 1.4-M4
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
