felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-4941) Configuration Properties not defined in Metatype are lost after update
Date Tue, 31 May 2016 07:24:12 GMT

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

Carsten Ziegeler resolved FELIX-4941.
    Resolution: Fixed

I've updated the web console to leave all properties not covered by metatype as-is

> Configuration Properties not defined in Metatype are lost after update
> ----------------------------------------------------------------------
>                 Key: FELIX-4941
>                 URL: https://issues.apache.org/jira/browse/FELIX-4941
>             Project: Felix
>          Issue Type: Bug
>          Components: Web Console
>    Affects Versions: webconsole-4.2.8, webconsole-4.2.14
>            Reporter: Cliff Collins
>            Assignee: Carsten Ziegeler
>             Fix For: webconsole-4.2.16
> Web console when updating items that have metadata will only update the properties defines
in metadata.
> This means, the fileinstall file location is removed from the property update. This makes
so fileinstall will no longer update the configuration
> file with the change. A simple workaround is to always post back the fileinstall property
if present. 
> In the ConfigAdminSupport.java file added these lines. In the method applyConfiguration
at line 312, insert these lines:
>             // Add Fileinstall key or the property will not get written back to the configuration
>             if (props.get("felix.fileinstall.filename") != null)
>             {
>                 updateProps.put("felix.fileinstall.filename", props.get("felix.fileinstall.filename"));
>             }
> If you return the fileinstall filename then fileinstall will save any property changes.

This message was sent by Atlassian JIRA

View raw message