Overview
Features
Download
Documentation
Community
Add-Ons & Services

Do not create configuration key on read access!

Discussion of ideas for features and new projects based on POCO.

Do not create configuration key on read access!

Postby mehdix » 09 Jun 2008, 20:32

Hi

First of all, thanks for your great work!

The problem is best explained through an example:
Given an object of WinRegistryConfiguration that contains the following keys:
||config.val1|
config.sub.val2 | ||
execution of this line:
winRegConfig->createView("config")->getString("sub.val3", "Default value");
causes an extera 'sub' key created in wrong place in 'winRegConfig':
||config.val1|
config.sub.val2 |
__sub__ | ||

I've composed a readonly (PropertyFileConfiguration) and a writable (WinRegistryConfiguration) configuration class through LayeredConfiguration, so that the writable config will be searched first (has lower priority).
This composition worsen the problem: when I read a key that only exists in readonly config, its parent keys are also created in the writable config!

Regards.
mehdix
 
Posts: 2
Joined: 06 Jun 2008, 19:40

Re: Do not create configuration key on read access!

Postby mehdix » 21 Jun 2008, 13:23

Any comment about this?
mehdix
 
Posts: 2
Joined: 06 Jun 2008, 19:40

Re: Re: Do not create configuration key on read access!

Postby alex » 07 Jul 2008, 01:21

> Any comment about this?

I have created a bug report for it.
alex
 
Posts: 1087
Joined: 11 Jul 2006, 16:27
Location: United_States


Return to Wishlist

Who is online

Users browsing this forum: No registered users and 3 guests