Re: Character Encoding Error using new filters

2010-10-20 Thread Zoran Avtarovski
I have set UTF-8 as the default everywhere - struts, tomcat, sitemesh. I had a small breakthrough. It looks like it's a 2.1.6 specific issue. I updated a development version to 2.1.8 and 2.2.1 and both worked fine. I now have to find time to test the updated version for unintended consequences.

Re: RE: Character Encoding Error using new filters

2010-10-18 Thread Dave Newton
That defines the encoding of the web.xml file itself... On Oct 18, 2010 10:32 AM, "Martin Gainty" wrote: > > Hi Zoran > > can you confirm the encoding attribute at the top of your web.xml e.g. > > > in which case you *should* be able to map > U+00C6Æc3 86LATIN CAPITAL LETTER AE > http://www.utf8-

RE: Character Encoding Error using new filters

2010-10-18 Thread Martin Gainty
Hi Zoran can you confirm the encoding attribute at the top of your web.xml e.g. in which case you *should* be able to map U+00C6Æc3 86LATIN CAPITAL LETTER AE http://www.utf8-chartable.de/ please confirm Martin Gainty __ Verzicht und Vertraulichk

Re: Character Encoding Error using new filters

2010-10-17 Thread Li Ying
Sorry, type error: > In your old configuration, [StrutsPrepareFilter] is the last filter applied > to request ==> Should be: In your old configuration, [FilterDispatcher] is the last filter applied to request 2010/10/18 Li Ying : > I did a quick look at the struts2.2.1 source code. > > It l

Re: Character Encoding Error using new filters

2010-10-17 Thread Li Ying
I did a quick look at the struts2.2.1 source code. It looks like the method [HttpServletRequest.setCharacterEncoding] is invoked by class [FilterDispatcher] and [StrutsPrepareFilter]. (You can use [Call Hierarchy] view to find out this information) In your old configuration, [StrutsPrepareFilter]