Really??? A filter just to set character encoding??? Although I imagine it
would work isn't that a little sledge hammer-ish ;-)
I seem to recall it was the recommended practice.
Why not just put the following at the top of each of your JSPs (or tweak as
necessary):
%@ page
Hi,
if I want to use indexed properties (using a Map) as parameter (by the
way: Thank you so badly for this feature. It just works so amazingly
easy and great). Is it possible to validate the key?
In my case the key is a string and I would like to validate it by
testing with a simple regex if
Hi Thomas,
You can validate your keys using a @ValidationMethod:
http://www.stripesframework.org/display/stripes/Validation+Reference#ValidationReference-CustomValidation
.
Cheers,
--
Samuel Santos
http://www.samaxes.com/
On Sat, Feb 5, 2011 at 11:55 PM, Thomas Menke
Hi Daniil,
I've an old post about this topic at
http://www.samaxes.com/2006/12/java-and-utf-8-encoding/.
Hope it helps,
--
Samuel Santos
http://www.samaxes.com/
On Sat, Feb 5, 2011 at 8:16 AM, Janne Jalkanen janne.jalka...@ecyrd.comwrote:
Really??? A filter just to set character
Janne and Samuel,
Ok... I think there are some things that need to be clarified... b/c it
was a while since I set this up in Stripes... I hadn't realized I even
set it up.
Technically speaking yes - you are both correct -
request.setCharacterEncoding(UTF-8) is required and should be
Hi Nikolaos,
My post was about Java EE in general and not about Stripes.
With Stripes, a custom LocalePicker implementation will correctly encode
POST parameters, but you still need to add the URIEncoding=UTF-8 attribute
to your connector configuration.
Cheers,
--
Samuel Santos
Hey Samuel,
Samuel Santos wrote:
Hi Nikolaos,
My post was about Java EE in general and not about Stripes.
This mailing list is about Stripes not Java EE in general :-)
Sorry - couldn't resist - just joking with you :-)
But the OP was asking about UTF-8 with Stripes et al. and both Janne and
