This week's giveaway is in the Java/Jakarta EE forum.
We're giving away four copies of Java EE 8 High Performance and have Romain Manni-Bucau on-line!
See you should be able to get a feel for the best way to go in your situation.
HTH, Guy
Saloon Keeper
Posts: 19078
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Multilingual JSPs are a forte of the Struts application framework - you define the resources in a properties file and use Struts tags to refer to the properties.
For a quick into to Struts, I humbly recommend the article I wrote for the April 2002 Java Pro magazine, which is presently readable online at - please forgive the typo - I consistently referred to the "perform()" method in the Action classes as "process()". Other than that, it should be reliable.
You can find Struts at
JeanLouis Marechaux
Ranch Hand
Posts: 906
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think I misexplained my problem.
I know how to put i18n in my application.
Actually, I will (and I already)use Struts for localized messages and contents but the question is:
What is the best practice ?
Is it really interesting to dynamically create all the parts of my page or is it better to have 2 different pages for 2 different languages.
Let's say I have an array with some buttons in my page. Am I going to read the header of the columns from a resourcebundle ? I know I can do it but is it valuable ?
And what about the design problem it can raise.
If the name of my column is 5 characters in english and 20 in spanish, maybe the header will be shorten ?
Same problem with a button name or a label of a sle or a mle.
I am wondering if it could be better to have JSPs in english and another set of JSPs in spanish.
Of course, all dynamic content (data, messages) will ALWAYS be in a resourcebundle and inserted dynamically.
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!