PrimeFaces 3 and Internationalization

[oranheim]

Hi Optimus,

I compiled latest svn anno sources and found that it breaks with Internationalization. My Norwegian special characters is not received correctly and text is displayed with wrong encoding. It's wierd because the input control I fill in 'øæå' in is a plain JSF input. Howcome, PF interfers with form data in general. My form do have several other PF components at it.

Due to the new fileUpload, it would be really great to start using. Is this a known bug with PF 3 M2-SNAPSHOT.

I hope this will be fixed soon!

Let me know, if you want me to file a bug report.

Cheers,
Ove

Env: JBoss 6, Seam 3 and Mojarra JSF 2.0.3.b05.

[oranheim]

Upgraded to 3.0.M2 and the same error still persists.

In 2.2.1 characters are encoded correctly, but in 3.0.M2 they are not handled correctly.

Norwegian letter å translates into Ã¥.

Added a CharacterEncodingFilter to force UTF-8, but still it won't work.

Any ideas?

[cagatay.civici]

Can't replicate at;

http://www.primefaces.org/showcase-labs/ui/editor.jsf

[oranheim]

I have added a character encoding filter and I disagree. This is reproducible. Your test case is based on GlassFish and PrimeFaces only.

If you add Seam to it, it doesn't work. I filed an issue related to this posting at: http://code.google.com/p/primefaces/iss ... %20Summary

And I think it should be reopened and further investigated. Can it be something wrong in the filter chain for encode/decode of UTF-8 char encoding? And why should developers using PF have to add a char encoding filter? Wouldn't it make sense to have this as an internal to PF?

PrimeFaces 3 M2 breaks localization in other app server environments than GlassFish / PF. Tried it again with JBoss 7, Mojarra 2.0.4 b09, and Seam Solder 3.0.0 + Faces 3.0.1.

This seems to be a showstopper for CDI development and PF.

Please let me know how I can be of help here.

[oranheim]

I found a solution to the internationalization problem.

This reason it didn't work was because CharacterEncodingFilter wasn't configured properly. The filter-mapping requires the url-pattern to be set to /* to in web xml.

Code: Select all

    <filter>
        <filter-name>Character Encoding Filter</filter-name>
        <filter-class>org.primefaces.examples.filter.CharacterEncodingFilter</filter-class>
    </filter>
    <filter-mapping>
        <filter-name>Character Encoding Filter</filter-name>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>

Now it works all fine

Ove

[cagatay.civici]

Thanks for sharing.