Few more thoughts on this matter: I haven't explicitly said that the solution I've proposed is far from standard i18n functionality, it was my best choice for the given example.
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. This way you'll get rid of the custom internationalization algorithms but it's definitely not the easiest way to go. The good thing about this solution is that you can go with it as far as adding new language for product names becomes a matter of simple configuration. Regards, Dimitar Vlasev. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
