[
https://issues.apache.org/jira/browse/SLING-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14136522#comment-14136522
]
Alexander Klimetschek commented on SLING-3909:
----------------------------------------------
Documentation and client-side code being aware of the right calls to make. IMO
it's a similar question you already have with the sling post servlet and jcr
content - should you know on the client side the JCR content structure or have
some minimal http interface with the minimum of parameters plus a custom
servlet and some custom domain objects that write to the JCR content as an
implementation detail. The former is perfectly fine.
> Merged ResourceProviders should be optionally modifiable
> --------------------------------------------------------
>
> Key: SLING-3909
> URL: https://issues.apache.org/jira/browse/SLING-3909
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Justin Edelson
> Assignee: Carsten Ziegeler
> Fix For: Resource Merger 1.2.0
>
>
> This is a continuation of the work originally started in SLING-3420.
> Modification are always done on the "most significant" resource (i.e.
> /apps/foo instead of /libs/foo) as determined by the MergedResourcePicker.
> The algorithm for modification is as follows:
> * Create - if the most significant resource doesn't exist, one is created at
> that path; otherwise an exception is thrown.
> * Delete - if the most significat resource doesn't exist, the hide children
> property is set on the most signfiicant resource's parent. if it does exist,
> it is deleted and the hide children property is set.
> * Property Modifications - most significant resource is created as necessary.
> ** Create - created on most significant resource
> ** Modify - created/updated on most significant resource
> ** Delete - deleted if necessary on most significant resource and hidden.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
