Smartly load your properties

Method	Parameter format	Lookup failure behavior	Usage example
ClassLoader. getResourceAsStream()	"/"-separated names; no leading "/" (all names are absolute)	Silent (returns null)	this.getClass().getClassLoader() .getResourceAsStream ("some/pkg/resource.properties")
Class. getResourceAsStream()	"/"-separated names; leading "/" indicates absolute names; all other names are relative to the class's package	Silent (returns null)	this.getClass() .getResourceAsStream ("resource.properties")
ResourceBundle. getBundle()	"."-separated names; all names are absolute; .properties suffix is implied	Throws unchecked java.util.MissingResourceException	ResourceBundle.getBundle ("some.pkg.resource")

and there're more tips in the linked resource below.

Resources

1. Smartly load your properties
   

Difference Between ResourceBundle and Properties Classes in Java

GMHK wrote:
> Can anyone tell me the whats the difference between the resource bundle
> and Properties classes in java.
> As both uses the .properties file to get the string constants.

No, they don't necessarily. A resource bundly does not have to be
file-based. The common implementation, however is. And that common
implementation (PropertyResourceBundle) indeed uses properties files and
thr Properties class.

However, resource bundles also come with a particular lookup-schema to
select a particular bundle according to the Locale. Something which you
don't get with Properties, but which is important when you do some
actual localization.

> At what point of time would the programmer decide to choose which of
> the either classes.

A resource bundle (properties file based or otherwise) when in need for
the lookup of locale-specific data. A naked properties file when in need
for keeping some small (FSWO) set of data persistent (e.g. application
configuration data), which is not supposed to be translated.

You didn't mention Preferences. I still preferen Properties over
Preferences because of the easy-to-work-with text file format, but they
can be used for the same purpose as Properties, without the need of
having to deal with files.

> What i understood so far is resourcebundle makes uses of String manager
> to get the string.
> where as the Properties tries to read the properties directly.

Both map keys to values. The biggest difference is how they get that
mapping. ResourceBundles follow a build-in lookup schema taking a locale
into account. Properties need to be provided with some InputStream,
which the programmer has to handle explicitely. Properties have an easy
way to be written to an OutputStream, while ResourceBundles are ment to
be read-only.

/Thomas

Resources

1. Difference Between ResourceBundle and Properties Classes in Java
   

Multiple Eclipse Installation Management

Resources

1. Managing plugins in eclipse.
2. Eclipse: Managing Multiple Eclipse Installation.
3. Setting up eclipse for painless upgrades.