Vincent van Beveren <[EMAIL PROTECTED]> wrote: > Ofcourse I could also build a tool, like the 'localeTool' and do the > following: > > $localeTool.getMessage($product.title) > > where $product.title would return some object that contains a string for > each locale, and LocaleTool would know how to extract the right string > from the bunch. But I find this rather verbose, and it makes the code ugly.
$msg.get($product.title) isn't all that verbose, to use the struts version. Unless you're going to build localization into every single object, you're going to need something of that form anyway -- A key that says what you want to localize, and a tool to do the localization. > In my case information is loaded from a database. That's just a hidden implementation detail, and not really part of the problem definition. I also load my info from a database, but it looks the same in velocity. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
