Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <10345261.1190565412188.JavaMail.jira@brutus>
Date: Sun, 23 Sep 2007 09:36:52 -0700 (PDT)
From: "Oliver Heger (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Updated: (CONFIGURATION-271) BaseConfiguration duplicates
 multi value keys values
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CONFIGURATION-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliver Heger updated CONFIGURATION-271:
---------------------------------------

         Priority: Minor  (was: Major)
    Fix Version/s:     (was: 1.5)
                   1.6
         Assignee:     (was: Emmanuel Bourg)
       Issue Type: New Feature  (was: Bug)

So far all our configurations have bag semantics, i.e. a value can occur multiple times for a single property.

If I understand this ticket correctly, you basically want to introduce set semantics, i.e. the values of a single property are unique. It should be possible to switch between the different modes.

I think, this is a good idea and certainly makes sense for certain use cases. However, implementing this feature in a clean way won't be a trivial task. Multiple configuration base classes will be affected. Because of that we probably won't be able to get this into the next release. So I am setting the fix version to 1.6

> 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.6
>
>
> 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.