aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Roman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1352) Do not overwrite existing configuration when installing a subsystem
Date Thu, 27 Aug 2015 14:10:46 GMT

    [ https://issues.apache.org/jira/browse/ARIES-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14716727#comment-14716727
] 

Alexandre Roman commented on ARIES-1352:
----------------------------------------

Here is a new patch with a unit test.

> Do not overwrite existing configuration when installing a subsystem
> -------------------------------------------------------------------
>
>                 Key: ARIES-1352
>                 URL: https://issues.apache.org/jira/browse/ARIES-1352
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>    Affects Versions: subsystem-2.0.1
>         Environment: Felix 5.0.1 / Aries Subsystems 2.0.2
>            Reporter: Alexandre Roman
>            Assignee: David Bosschaert
>              Labels: easyfix
>         Attachments: aries-1352-fix.patch
>
>
> I have a subsystem which embeds a configuration file (using "embedded-resource" and type="osgi.config.properties"
in the manifest file).
> When this subsystem is started, the configuration is applied, as expected.
> However, if a configuration file with the same PID is created, while the subsystem is
still not started, the configuration is overwritten by the subsystem resource on start.
> I think that ConfigAdminContentHandler should check if the configuration entries exist
before updating it from the subsystem resource.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message