[jira] Resolved: (FELIX-885) Saving a factory configuraiton instance creates a new instance instead of updating the old instance

["Felix Meschberger (JIRA)" <ji...@apache.org>]

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

Felix Meschberger resolved FELIX-885.
-------------------------------------

    Resolution: Fixed

The problem is the ConfigManager.getConfiguration(ConfigurationAdming, String, String) method which created a new factory configuration instance whenever factoryPid was not null. This is wrong, since a new instance should only be created if the pid is null or the placeholder pid used to create a temporary configuration instance used to build configuration form.

Applied fix in Rev. 735450 and deployed SNAPSHOT version 1.2.3-20090118.131353-3.

Keeping this issue open until I get feedback from the reporting user.

> Saving a factory configuraiton instance creates a new instance instead of updating the old instance
> ---------------------------------------------------------------------------------------------------
>
>                 Key: FELIX-885
>                 URL: https://issues.apache.org/jira/browse/FELIX-885
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>    Affects Versions: webconsole-1.2.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: webconsole-1.2.4
>
>
> When modifying and saving an existing factory configuration instance in the web console, a new instance is created with the new configuraiton values instead of updating the actual existing configuraiton instance with the new values.
> This behaviour has also been reported on the Sling Developers list [1]
> [1] http://markmail.org/message/4zelcrodtfisqa5m

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.