You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2011/03/01 09:18:36 UTC
[jira] Commented: (SLING-1971) Persist configuration (and bundle)
changes not made through the installer
[ https://issues.apache.org/jira/browse/SLING-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000768#comment-13000768 ]
Carsten Ziegeler commented on SLING-1971:
-----------------------------------------
I've added a first rough implementation in revision 1075697
This implementation handles configuration changes at least partially.
Before I can clean up, I'll first do SLING-1999 and split core and configuration handling
> Persist configuration (and bundle) 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
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
>
> 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