Thanks for the reply Actually, we do use a filter setting the encoding to UTF-8, though I'm not sure if my problem is exactly the same as above.
Sending a request form a JSP using ISO-8859-1 with POST method (no problem using GET method or UTF-8 on origin page) to either a Struts action or another JSP (with either UTF-8 or ISO-8859-1, tried both) replaces my å,ä and ö with '?', even though I've set the Connector property (Tomcat as server) to UTF-8. So the problem seems to happen with the POST data in the request when going from ISO to UTF using POST method... having ran my head against this encoding wall too long now, I'm hoping to get some clues from you guys... /Riffla Christopher Schultz-2 wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Riffla, > > riffla wrote: >> And I guess that the form bean attributes is set prior to any code in the >> form class, so that you can't set the characterEncoding in the form class >> (at, for example, the beginning of initialize() method), or...? > > Correct. You have to use a Filter to do this. Search the archives for > "character encoding filter" and you should find a lot of information, > including the code for the filter itself (or at least a link to the code). > > - -chris > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFGA8QY9CaO5/Lv0PARAn7AAJ4vklzBFWc2/m2Go6EHv68eGoe6LQCgrNcX > peNhqvneyvg8Fsmbn99nwEI= > =LZZ+ > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Character-encoding...-tf297678.html#a9634418 Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
