felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-4360) Ensure ordered property values in configurations
Date Sat, 28 Dec 2013 18:32:50 GMT

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

Felix Meschberger resolved FELIX-4360.

       Resolution: Fixed
    Fix Version/s: configadmin-1.8.2
         Assignee: Felix Meschberger

Added a test case validating value order of collection properties in Rev. 1553885

Internally all collection type properties are handled with Vector instances. Therefore order
is always preserved.

> Ensure ordered property values in configurations
> ------------------------------------------------
>                 Key: FELIX-4360
>                 URL: https://issues.apache.org/jira/browse/FELIX-4360
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin, Specification compliance
>    Affects Versions: configadmin-1.8.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: configadmin-1.8.2
> Older Configuration Admin Service specifications allowed multi-value properties to be
stored as either arrays or Vector objects. Recently the specification was changed to support
Collection objects.
> The problem is that vectors are sorted, much like lists, while collections do not define
an order.
> The upcoming specification release of the Configuration Admin Service will clarify that
configuration properties provided in a Collection object supporting ordering (e.g. Vector
or List) must maintain their order when persisted and provided back.
> For our implementation this should not be a problem since we are internally using ArrayLists.
Still we might want to cross check and implement a unit or integration test to validate the

This message was sent by Atlassian JIRA

View raw message