[
https://issues.apache.org/jira/browse/SLING-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012399#comment-13012399
]
Carsten Ziegeler commented on SLING-1971:
-----------------------------------------
I've changed the implementation in revision 1086523 a little bit: instead of
creating a node of type sling:OsgiConfig with properties for the configuration
values, a file/resource node is created containing the same output as the
configuration admin is writing into the file system.
This is necessary as we need to keep property types like Integer, Char or
Vector/Collection values which are all not supported by the repository.
> Persist configuration changes not made through the installer
> ------------------------------------------------------------
>
> Key: SLING-1971
> URL: https://issues.apache.org/jira/browse/SLING-1971
> Project: Sling
> Issue Type: New Feature
> Components: Installer
> Affects Versions: Installer Core 3.1.0, JCR Installer 3.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Installer Core 3.2.0, JCR Installer 3.1.0
>
>
> Currently, config and bundle changes done through other ways than the
> installer (like web console) are not persisted - sometimes creating confusion
> and making changes for example in a clustered env more error prone.
> The providers should register a write back hook and the installer core
> detects changes and invokes the correct hook to persist the configuration
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
