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 -----Original Message----- From: Mircea Militaru [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 07, 2006 6:41 AM To: Tapestry users Subject: getMessage problem We have a small problem while migrating from T3 to T4. In T3 getMessage(..) was called to get keys from property files. By doing our own getMessage function we could use multiple property files and search for that key in each file. Is there a way to use multiple property files for the entire application ? The check would still be done first on the properties file for the component/page and than check the res of property files. Regards --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
