Actually it isn't that. We actually manage our internationalization in applicationMessage_en and our build script performs a copy of this file to applicationMessages. This should prevent what you're referring to.
Lets say our table column key is 'page.mytable.header.ponumber'. This key is defined in our applicationMessages_en property file but it is not in the applicationMessages_de file. When a user logs into the application using a locale of de_DE, the standard s:text and other tags take the lookup values from the en property file as it should; however, my code snippet earlier does not. It simply says it cannot find the key. Expectation is the following: en file: -------- page.mytable.header.ponumber=PO Number de file: -------- # page.mytable.header.ponumber does not exist jsp file: --------- <display:column titleKey="page.mytable.header.ponumber" /> Regardless of the Locale in the browser, I would expect this column to be shown with "PO Number" and not "PO Number" for English and showing the key value for the German locale. Chris -----Original Message----- From: Lukasz Lenart [mailto:lukasz.len...@googlemail.com] Sent: Monday, February 22, 2010 10:10 AM To: Struts Users Mailing List Subject: Re: DisplayTag and Internationalization Lookups Maybe it's related to that https://issues.apache.org/jira/browse/WW-3219 --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
