felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3231) Disable update counter
Date Thu, 17 Nov 2011 10:08:51 GMT

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

Felix Meschberger resolved FELIX-3231.
--------------------------------------

    Resolution: Fixed

Removed the lastUpdateTime field (and all references and uses) and renamed the lastModificationTime
field to revision to reflect the intended use as a revision counter rather than a timestamp.
                
> Disable update counter
> ----------------------
>
>                 Key: FELIX-3231
>                 URL: https://issues.apache.org/jira/browse/FELIX-3231
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin, Specification compliance
>    Affects Versions:  configadmin-1.2.8
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: configadmin-1.4.0
>
>
> Update counter checks have been added to prevent multiple configuration updates with
the same configuration in certain race condition situations.
> With the new R4.3 Configuration Admin (v1.4) it is now allowed that multiple ManagedService
or ManagedServiceFactory services are registered with the same PID and that all receive the
same configuration. This of course is incompatible with the current simple update counter
mechanism.
> For now we should just disable this check.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message