Struts 2 is very flexible when it comes to organizing resource bundles
for i18n.
Is anyone experienced with i18n issues in a *large* struts 2 application
able to share what you've found to be an effective way to organize these
resources? And preferably why you've arrived at that conclusion?
eg. global resources vs package vs action vs model, consistent naming
conventions, use of the text and i18n tags
I know the answer is "it depends" which is why I'm especially interested
in the why part of the answer. Any insight you can provide will be
greatly appreciated!
regards,
Jeromy Evans
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
