commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CONFIGURATION-271) BaseConfiguration duplicates multi value keys values
Date Sun, 21 Jun 2009 22:28:07 GMT

    [ https://issues.apache.org/jira/browse/CONFIGURATION-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722431#action_12722431
] 

Emmanuel Bourg commented on CONFIGURATION-271:
----------------------------------------------

I don't see how this could be implemented. If there is a way to tell a given property has
a set semantic, it has to be persisted to the backend. And that's impossible with most of
the configuration formats (properties, plist, INI, map, database, jndi). It may be possible
with an XML configuration by adding some metadata to the output like a specific attribute
on the xml node (for example <foo config:collectionType="set">). But that would not
solve the original issue.

> BaseConfiguration duplicates multi value keys values
> ----------------------------------------------------
>
>                 Key: CONFIGURATION-271
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-271
>             Project: Commons Configuration
>          Issue Type: New Feature
>    Affects Versions: 1.4
>            Reporter: Daniel Adrian
>            Priority: Minor
>             Fix For: 1.7
>
>
> In addPropertyDirect(String key, Object value) the method adds the new value to the property.
> If the property has the same value in the list, it will get duplicated.
> The method should check if the list contains the value and only if the result is false
add the value. 
> There is no logic in saving a multi value key with more than one instance of a value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message