You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2008/04/19 17:22:21 UTC
[jira] Resolved: (CONFIGURATION-276) java.util.prefs Configuration
[ https://issues.apache.org/jira/browse/CONFIGURATION-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger resolved CONFIGURATION-276.
----------------------------------------
Resolution: Fixed
A new PreferencesConfiguration class has been added that allows accessing Preferences nodes as a hierarchical configuration.
> java.util.prefs Configuration
> -----------------------------
>
> Key: CONFIGURATION-276
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-276
> Project: Commons Configuration
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Michael Rudolf
> Assignee: Oliver Heger
> Priority: Minor
> Fix For: 2.0
>
>
> Hi,
> I have read that Commons Configuration is intended to be compatible with Java 1.3 but would it be possible to create a configuration backend for the Preferences API provided since Java 1.4?
> In my project I would like to use a very low-overhead configuration mechanism as is the Preferences API while still having the flexibility and power offered by Commons Configuration. In fact, being able to swap in a config file for testing purposes without changing the code would be wonderful. However, I do not like the idea of providing the end user with such a file or even a database, changing application settings should be done through the UI.
> If it is not possible to add a preferences backend to the code base due to the backward compatibility policy, could such a backend then possibly be provided in another branch or in a subproject?
> Best regards,
> Michael
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.