LF 6.0.6 on Glassfish 3.1 - Problems with I18N

• Type: Bug
• Status: Closed
• Resolution: Won't Fix
• Affects Version/s: 6.0.6 GA
• Fix Version/s: 6.0.6 GA
• Component/s: Environments > App Servers
• Labels: None
• Environment: LF 6.0.6 CE, Glassfish 3.1, Mac OS X 10.6.7
• Similar Issues: Show 5 results ; ;

  LPS-24500	Richfaces portlet can't work on Liferay 6.1 (it could on LF 6.0.6)
  LPS-17002	Upgrade to GlassFish 3.1
  LPS-26423	JBoss 7.0 / Glassfish 3.1 / Jonas 5.2 will throw exceptions on shut down.
  LPS-20094	Communities lost (deleted) after upgrade 5.1.1 to 6.0.6.
  LPS-40183	Unable to Open Public Pages in Site and Page Templates on Glassfish 3.1

Hello,

I have deployed a LF 6.0.6 war distribution on a Glassfish 3.1 server. Everything works fine except that I can't get international (french éàèç or german äöü) characters to display correctly.

When looking at the page's source code, I can see the <meta content="text/html; charset=UTF-8" http-equi="content-type"/>

The http listeners in GF 3.1 are set to UTF-8. MySQL is set to UTF-8 and the jdbc connection string has the encoding set to UTF-8.

The problem is not limited to labels coming from MySQL (like page names) but also labels coming from the language properties files.

Also, when in the Control Panel - Manage Pages, I can see the special characters correctly displayed in the pages tree view, but not in the detailed view on the right side.

I also noticed that the GF bundle only contains a GF 3.0.1.

Is there a problem with GF 3.1 and is there a solution to make the special characters display correctly?

[Fernando Correia]

I have the exact same issue as reported (in Portuguese) at http://www.liferay.com/pt/community/forums/-/message_boards/message/10005372

[Alex Weirig]

Hello,

I think you can close this ticket. 6.0.6 is kind of old and I haven't tested with 6.1.0.

Alex

[Yordan Nalbantov]

It's actually a Glassfish issue. See http://java.net/jira/browse/GLASSFISH-18516
Liferay 6.1.0 CE B4 with GF 3.1.1 should work just fine.

[Alex Weirig]

Hello,

I think we should close this ticket.