5 Replies Latest reply on Nov 24, 2010 4:29 AM by nickarls

    i18n of JSF/facelets/EL

    nickarls

      Hi,

       

        Where could I start looking for information on how to be able to use iso-8859-1 in EL and facelet template names? I have set the URIEncoding on the connector on my AS 6 M4 but I still have problems using EL-method names, facelets names and JSF 2 resources that contain ISO-8859-1 chars...

        • 1. Re: i18n of JSF/facelets/EL
          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

            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

              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.

              • 4. Re: i18n of JSF/facelets/EL
                nickarls

                BTW, was this reproducable for you?

                • 5. Re: i18n of JSF/facelets/EL
                  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)