3 Replies Latest reply on Jun 3, 2009 6:39 PM by Vladimir Kovalyuk

    Seam Wicket integration and request parameters UTF-8 encoding problem

    Vladimir Kovalyuk Apprentice

      Due to IE bug deliberately replicated among all the other browsers we have org.jboss.seam.web.CharacterEncodingFilter.

      In fact it is installed only with ajax4jsfFilter. So it does not work with pure Wicket UI.

      Actually Wicket does not need yet another utf-8-fix-filter since original WicketFilter class already adresses this issue. But the fix does not work because ContextualHttpServletRequest touches request parameters (at least to restore conversation useless in wicket environment) before WicketFilter calls request.setCharacterEncoding(UTF-8).

      It is no doubt a bug in Seam WicketFilter implementation.

      To fix that in Seam you can free CharacterEncodingFilter from JSF and install it with Wicket.

      As a workaround you can follow the steps described in the following article: http://wiki.apache.org/tomcat/Tomcat/UTF-8