To add to that, take care that the life cycle for both configurations is
different. Preferences belong to a bundle, if the bundle goes away, so do its
preferences. ConfigAdmin keeps configurations around (before or after the
actual service bundle is installed).
Based on your brief requirements,
My view is slightly different:
* ConfigAdmin is for externally managed configuration data.
* PreferencesService is for application managed preferences and
settings.
But, I agree, I think you could use either depending on the specific
scenario.
-> richard
On 2/5/10 6:45 PM, Andreas
Hi Craig,
The config admin stuff is used for per-installation configuration of
individual services. The preferences is more appropriate if you need
to store per-user settings for the same installation. At least, that's
how I think of them.
For a swing application, I assume you'll have a 1-to-1 r
Hi,
I am developing a plugin model for a Swing based application.
The plugins are currently being deployed as OSGi Services and these services
will need to be configured by each individual user for their local
requirements/environment etc. using the Swing UI. This configuration data
will need to
4 matches
Mail list logo
