2010/1/10 Jos Snellings jos.snelli...@pandora.be
This is not a specific cocoon issue, I believe. It probably has to do
with Tomcat 5.5.27.
request.setCharacterEncoding simply does not work; it does not change a
thing.
request.getCharacterEncoding returns nothing.
You have to call
Thanks, I will try CharacterEncodingFilter!
I will lookup in the code were filtering takes place, because the
problem is rather that it looks like the form data are filtered twice.
In addition, do I remember right that there used to be a cocoon servlet
setting,
init-param
On Mon, Jan 11, 2010 at 9:12 AM, Jos Snellings jos.snelli...@pandora.bewrote:
Thanks, I will try CharacterEncodingFilter!
I will lookup in the code were filtering takes place, because the
problem is rather that it looks like the form data are filtered twice.
In addition, do I remember right
Jos Snellings wrote:
Hi,
HttpServletRequest looks 'imperfect':
Cocoon 3, alpha 2.
A generator accesses the HttpServletRequest in the setup method:
request = HttpContextHelper.getRequest(parameters);
text = request.getParameter(tekst);
The pages, including forms are ecoded in utf-8.
This, to notify you that the solution you suggested works fine:
So, for all cocoon users: if you are experiencing problems with the
character encoding of POST form data (which is very likely to occur):
the problem is generally cured by
Inserting the following code in web.xml
filter
That is right!
It is just a confusing situation :-(
The filter works fine. The init() method of a generator does not give a
chance to call setCharacterEncoding, as the parsing already happened.
The good thing is that the code is already in spring, so, no new
external dependencies. Maybe later on I
On Mon, Jan 11, 2010 at 10:34 AM, Jos Snellings jos.snelli...@pandora.bewrote:
That is right!
It is just a confusing situation :-(
The filter works fine. The init() method of a generator does not give a
chance to call setCharacterEncoding, as the parsing already happened.
The good thing is
This is not a specific cocoon issue, I believe. It probably has to do
with Tomcat 5.5.27.
request.setCharacterEncoding simply does not work; it does not change a
thing.
request.getCharacterEncoding returns nothing.
Best,
Jos
On Sat, 2010-01-09 at 08:01 +0100, Jos Snellings wrote:
Hi,
Hi,
HttpServletRequest looks 'imperfect':
Cocoon 3, alpha 2.
A generator accesses the HttpServletRequest in the setup method:
request = HttpContextHelper.getRequest(parameters);
text = request.getParameter(tekst);
The pages, including forms are ecoded in utf-8.
The String 'text' is strange: the
