Package org.xissweb.prefs

Why another preferences management instead of the Java's one?

See:
Description

Class Summary

PreferencesManager

This class can manage different kinds of preferences (by example, user and system preferences).

Package org.xissweb.prefs Description

Why another preferences management instead of the Java's one?

4 reasons to this:

1. The first reason is the compatibility from Java 1.4 to 6 and Xerces libraries. The XML export of nodes isn't totally compatible in this context.
2. This implementation is a completely Java and platform independent. The unique dependence with a platform is the file system (used to make preferences persistent).
3. This class manages a simple correspondence between a class (called a configurable class) and a set of parameters. It doesn't manage hierarchy of nodes has Java's management do.
4. The client decides where to store its preferences and it's doesn't need a special platform resource, only the file system.

You're already used Java's preferences management, it corresponds to your need and no of the above reasons is applicable, don't change!