[
https://issues.apache.org/jira/browse/FELIX-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180538#comment-15180538
]
John Ellinwood commented on FELIX-4941:
---------------------------------------
Is this still an issue with 4.2.15? This is a pretty bad issue. We have a lot
of configuration we drop in with fileinstall... then users will go to the
webconsole to refine the properties. As soon as they do that, the config pid
is now completely disconnected from the backing file. The worst part is that
if you restart felix/karaf, fileinstall will see the file and reinstall it so
now you have 2 separate configurations which breaks a lot of things.
> Web console doesn't work with fileinstall
> -----------------------------------------
>
> 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
> Labels: easyfix
>
> 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
(v6.3.4#6332)
