[
https://issues.apache.org/jira/browse/ARIES-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Roman updated ARIES-1352:
-----------------------------------
Attachment: aries-1352-fix.patch
Here is a patch for this issue.
If a configuration exists when the subsystem is started, the new configuration
is not applied.
> 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
> 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)
