> > If the "Product" described in the first message is pure fiction and > you have the ability to change the data model you can get rid of the > multiple names from the "Product" entity, put a "unique_name", use it > to point to resource in your bundle with some static prefix like > "product.name.". > The actual names of the items you'll store like standard message resources. > You can even use database message resources if you are not fan of the > properties files. >
In essence, this is how SAP R/3 handles internationalisation. Strings like the product description are stored in a seperate database table with the locale as part of the index. So, in the example of the product table, there is a seperate table consisting of product_code, locale and descriptive text indexed on product_code and locale. If you can pass the locale code into your DAO layer then you shouldn't need to alter your application when you add new languages. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
