Thankx for the quick response.
We have tried creating an application properties file and this way is
working. Is there any other way to be able to set more properties file
for an application ?
From
http://jakarta.apache.org/tapestry/UsersGuide/localization.html#localization.namespace
> It is very likely that you'll have a number of strings that are used,
and re-used, throughout your application. Rather than duplicate the same
message keys and localized values in all your page and component message
catalogs, you can put these into your /namespace/ catalog.
Is there a way to use multiple catalogs for an application ?
Greg Cormier wrote:
Hi Mircea,
I just went through this. With T4 you have a glocal properties file as well as
a properties file for each page. I'm not sure if this will be good enough for
you, but it worked out nicely for us. Basically you name your properties file
the same as your application config file, so if you have
aWebApp.application
then you would make aWebApp.properties, aWebApp_fr.properties.
Then of course each page has it's own properties file.
When you call getMessage().getMessage(aKey), it will check the page file for
that key, and if it's not found, it will fall back to the application
properties file.
If you wanted more then this, you might have to do some coding and I'm not sure
how it would be done.
Greg
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
