|
02/28/2005 | |||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Package Summary
| Interface Summary | |
| Settings | This interface defines a Settings object -- a collection of name value pairs similar to a java.util.Map (which Settings extends), but with the additional feature of a "secondary value". |
| Class Summary | |
| SettingsManager | This class manages instantiation, cluster support, default values, and in-VM change notification for Settings objects. |
| Exception Summary | |
| SettingsException | |
| SettingsNotFoundException | |
Persists name/value pairs and name/value/secondary value tuples. The
simple name=value format is comparable to that provided by the
java.util.Properties class as well as the Preferences API of
Java 1.4. The additional name=value1,value2 format supports a
secondary value for a named property. Two APIs that use this secondary
value are Sites (to flag whether system-level settings are overrideable at
the site level and to store URL-to-site mappings at the system level) and
Internationalization (to store an optional comment for every localizable
resource).
A Settings object is a collection of
name=value1,value2 properties. The Settings
interface extends the
com.epicentric.uid.UniquelyIdentifiable interface. References
can therefore be stored for any Settings object.
Settings objects can also be placed into categories, providing
functionality similar to the Java 1.4 Preferences API. However, unlike the
Preferences API, Settings objects are not required to have
namespaces, as they can be easily indexed by their UIDs alone.
|
02/28/2005 | |||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||