File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes XML and Related Technologies and the fly likes Use XML or properties as a Java Localization Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Make it so: Java DB Connections & Transactions this week in the JDBC forum!
JavaRanch » Java Forums » Engineering » XML and Related Technologies
Bookmark "Use XML or properties as a Java Localization" Watch "Use XML or properties as a Java Localization" New topic

Use XML or properties as a Java Localization

Jeppe Sommer
Ranch Hand

Joined: Jan 07, 2004
Posts: 270
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:


[ 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
I agree. Here's the link:
subject: Use XML or properties as a Java Localization
It's not a secret anymore!