If I am not mistaken, under Servlet 2.3 spec, you can call the setCharacterEncoding() method on the request and set it to a desired encoding before reading any parameters from the request. The container is responsible for providing you with request parameters in the encoding your specified from this point on. WAS 4.0 does not support the J2EE 1.3 spec (it supports 1.2.1). You will need WAS 5.0 for this to work. It is working in Tomcat because the version of Tomcat you have supports J2EE 1.3.
----- Original Message ----- From: "Gemes Tibor" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, January 15, 2003 4:46 AM Subject: Re: AW: AW: AW: AW: Transforming a String to valid HTML encoding 2003. janu�r 15. 11:32 d�tummal Hirschmann, Bernhard ezt �rtad: > I think I have to study this in more detail - it still isn't quite clear > for me. > What is this SetCharacterEncoding filter doing? Is it only working with > Tomcat? (We use WebSphere 4) I don't know websphere, but if it conforms to the servlet specs v2.3 then it is. > I also have unicode characters from the DB which have to be displayed > correctly. Is this filter good for that? No. It is for the user submitted data to convert into the proper encoding. Tib -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.435 / Virus Database: 244 - Release Date: 1/1/2003 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
