1) no need to use spring
2) It's easy if you take a look at the source of
org.apache.tapestry.services.impl.ComponentMessages and its base class
org.apache.hivemind.impl.AbstractMessages
It's then a matter of:
a) overriding public String getMessage(String key) and when the key isn't
found, search
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Koeberl wrote:
> There are two good practices to do database i18n:
> http://www.theserverside.com/tt/blogs/showblog.tss?id=HibernateInternational
Christian,
thanks a lot for this link, esp. the first one is quite interesting!
I like it becau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Andreou wrote:
> http://wiki.apache.org/tapestry/HowTos
>
> see the Resources / I18n section
Andreas,
thank you for the link!
Two further questions:
1. Do I need Spring to do it? (we're not using Spring)
2. I want all my tapestry component
There are two good practices to do database i18n:
http://www.theserverside.com/tt/blogs/showblog.tss?id=HibernateInternational
http://java.sun.com/blueprints/guidelines/designing_enterprise_applications_2e/i18n/i18n5.html
We do quite the same with just one table for all texts.
Cheers,
Chris
http://wiki.apache.org/tapestry/HowTos
see the Resources / I18n section
On Wed, May 28, 2008 at 4:02 PM, Bastian Voigt <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear *,
>
> in my application I have lots of persistent objects (regions, cities,
> countries, et
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear *,
in my application I have lots of persistent objects (regions, cities,
countries, etc), from the database which are used in
PropertySelectionModels and other UI elements.
My approach for localizing the names was to give them a "key" field
whic
