-
1. Re: i18n of JSF/facelets/EL
nickarls Aug 31, 2010 1:32 AM (in response to nickarls)Any help would be... helpful as I suspect lots of this stuff is behind one configuration parameter. I also noticed that Bean Validation fails on EL-fields that have iso-8859-1 fields. Works fine when the validation is bootstrapped from SE.
-
2. Re: i18n of JSF/facelets/EL
ssilvert Aug 31, 2010 8:56 AM (in response to nickarls)Nicklas,
Can you provide an example of what you are trying to do?
You say it works fine when validation is bootstrapped from SE. Can you elaborate on that as well?
Stan
-
3. Re: i18n of JSF/facelets/EL
nickarls Sep 16, 2010 6:58 AM (in response to ssilvert)Given the attached example, you are redirected to ä.xhtml fine but any postback fails with the resource not being found. If you rename it to "a.xhtml", you will find that validation fails for the "aa" field but not for the "åå" field even if they have identical validation. If you run the main method from SE, you will see two (correct) failures to validate.
-
i18n.zip 8.5 KB
-
-
4. Re: i18n of JSF/facelets/EL
nickarls Nov 2, 2010 5:09 PM (in response to nickarls)BTW, was this reproducable for you?
-
5. Re: i18n of JSF/facelets/EL
nickarls Nov 24, 2010 4:29 AM (in response to nickarls)I'm still very interested in this. If a put a iso-8859-1 id on my input component, it even appears as if the value is never flushed to the model. I can save my model (the underlying attribute never changed, the invalid value is still left in the input)