Understanding preference optionsAdded by IBM on October 4, 2010 | Version 1 (Original)
|Preferences provide the ability for applications to be configured and managed using one of the provided management systems, and eliminate the need to change source code or plug-in contents to change application parameters.
Preferences provide the ability for applications to be configured and managed using one of the provided management systems, and eliminate the need to change source code or plug-in contents to change application parameters.
While there are several preference models, developers are strongly encouraged to use the Eclipse preference model, either directly, or through the Managed Settings provider. The OSGi Configuration Admin model in particular is deprecated, and support for it is likely to be removed in a future release.
Eclipse preference information: XPD621
The Eclipse framework provides an extensible preference store that permits preference information to be stored at various levels.
Configuration admin: XPD621
The OSGi core framework also provides a configuration management capability known as Configuration Admin. Configuration Admin provides capabilities to store preference or configuration information based on key value pairs. However, although the OSGi Configuration Admin service is still technically supported by the Lotus Expeditor Client, its use is deprecated, and support is likely to be removed in a future release. You should update any existing components that use Configuration Admin to use Eclipse preferences instead, and use Eclipse preferences for new components.
OSGi preference service: XPD621
The OSGi Preference Service defines a preferences model for OSGi Services. The OSGi Preferences model enables services to maintain their own preferences information, but the information is not available to other services or bundles, unless access is provided by the service itself.
Parent topic: Using preferences: XPD621