[prev in list] [next in list] [prev in thread] [next in thread]
List: jakarta-commons-dev
Subject: DO NOT REPLY [Bug 28660] New: -
From: bugzilla () apache ! org
Date: 2004-04-28 15:30:36
Message-ID: 20040428153036.29310.qmail () nagoya ! betaversion ! org
[Download RAW message or body]
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28660>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=28660
[Configuration] Lists in a CompositeConfiguration
Summary: [Configuration] Lists in a CompositeConfiguration
Product: Commons
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Configuration
AssignedTo: commons-dev@jakarta.apache.org
ReportedBy: christian@siefkes.net
Not sure whether this is a bug, but at least it's an issue where the
documentation differs from the actul behavior:
The CompositeConfiguration javadoc states:
"If you add Configuration1, and then Configuration2, any properties shared will
mean that Configuration1 will be returned.... If Configuration1 doesn't have the
property, then Configuration2 will be checked."
So this would mean, if a use getList or getStringArray I only get the list
elements from conf1 but not those from conf2, if the requested property is
contained in both. In reality, however, I get a combined list of the values
specified in conf1 + conf2 + any others.
I think it would be better to behave according to the documentation and to
return only the elements from the first matching configuration + any dynamically
added elements from the InMemoryConfiguration.
So, is this a bug, and will it be fixed?
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic