Hi Mike,
Mike Kienenberger wrote:
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.
In my case $msg.get would have to request the message from the database
on the basis of the message. Suppose (which is not at all unlikely in my
situation) that we're talking about a database with 250.000 products.
Each product has mutliple internationalized texts (description, title,
etc...) , even with only two messages per product this would result in
500.000 entries. It would not be convinient to create a code to message
mapping. Showing just a list of search results would be an huge strain
on the database. The objects themselves would need to know their
messages in different languages, that would be more convinient.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
