| Author |
Use XML or properties as a Java Localization
|
Jeppe Sommer
Ranch Hand
Joined: Jan 07, 2004
Posts: 263
|
|
Can anyone tell me the advantages or disavantages of using XML vs the properties file solution (the normal java ResourceBundle, where the translation is read from a properties file)?
When I think of advantages/disavantages I think about:
maintenance
performance
scalability
...
Thanks
[ June 13, 2005: Message edited by: Jeppe Fjord ]
|
 |
Madhav Lakkapragada
Ranch Hand
Joined: Jun 03, 2000
Posts: 5040
|
|
Personally I would go with XML instead of a Java Resource Bundle.
Self-explanatory, any one with basic HTML knowledge can change the properties - think about the folks in the field. The moment things are Java'ish, people are a bit more hands-off - its programming I don't understand all that stuff. This ResourceBundle thingy sounds more like Java Programming rather than a simple text file (assuming that's how you are implementing, hard to say).
Now that the JDK has support for XML, you don't need a lot of third-party tools for using it. More easy to maintain, IMO. This sounds more like the norm - look at any config files that application use - they are invariably in XML so its pretty much an industry standard.
My two cents...
- m
|
Take a Minute, Donate an Hour, Change a Life
http://www.ashanet.org/workanhour/2006/?r=Javaranch_ML&a=81
|
|
 |
|
|
subject: Use XML or properties as a Java Localization
|
|
|
0
