I am attempting to use a global application.properties file to specify the translations for localized strings in my component files but so far I have not been able to get tapestry to perform as documented.
For more background information on what I am referring to see the following documentation and closed jira issue: http://jakarta.apache.org/tapestry/UsersGuide/localization.html (see Namespace message catalogs) http://issues.apache.org/jira/browse/TAPESTRY-242 I am using tapestry 4 beta13, here is a little bit about my setup. I have myapp.application and in the same directory (WEB-INF) myapp.properties which includes name/value pairs. Inside of a component I am trying to translate some text using: getMessages().getMessage(key) I have verified the key exists in myapp.properties however the result is [KEY]. Am I using this feature incorrectly or is this a tapestry bug? I was not able to find anything in jira besides tapestry-242. Thanks! Ryan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
