[
https://issues.apache.org/jira/browse/SLING-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007994#comment-13007994
]
Tobias Bocanegra commented on SLING-1971:
-----------------------------------------
> For new configurations (configs which haven't been in the repository before),
> a path is configurable. By default new configs go to /apps/sling/config
can the path be guessed from the respective bundle location? e.g. if the bundle
location is /apps/myapp/install/abc-1.0.jar, the config should go to
/apps/myapp/config/...
> 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
