This is an automated email from the ASF dual-hosted git repository.
sseifert pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-superimposing.git
The following commit(s) were added to refs/heads/master by this push:
new b201c78 update link, fix typo
b201c78 is described below
commit b201c78af2e3cbdcd3502ebe52b2900ddec46313
Author: sseifert <[email protected]>
AuthorDate: Tue Mar 20 18:50:58 2018 +0100
update link, fix typo
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 4aa3710..fc5446a 100644
--- a/README.md
+++ b/README.md
@@ -51,12 +51,12 @@ In the Felix console you can configure the creation of
Superimposing Resource Pr
* The superimposing resource provider depends on an underlying JCR repository.
It currently does only work with JCR and supports mirroring or overlaying JCR
nodes.
* The Superimposing Resource Provider provides an API in the package
org.apache.sling.superimposing. For the basic superimposing content features
you do not need this API. It is a read-only API which allows to query which
superimposing resource providers are currently active with which configuration.
The API is useful if you want to react on JCR events on the source tree and
actions on the mirrored trees as well (e.g. for sending invalidation events to
clean an external cache).
-* If you want to use the superimposing resource provider within a CMS
application that allows to modifiy resource content via it's GUI make sure that
this CMS application supports this resource provider in it's authoring
environment (and does make direct JCR access, because this bypassed the
mirroring and affects the original JCR node - risk of data loss!). If you canne
be sure of this please activate the provider only on the sling instances that
render the content for the public (publis [...]
+* If you want to use the superimposing resource provider within a CMS
application that allows to modify resource content via it's GUI make sure that
this CMS application supports this resource provider in it's authoring
environment (and does make direct JCR access, because this bypassed the
mirroring and affects the original JCR node - risk of data loss!). If you
cannot be sure of this please activate the provider only on the sling instances
that render the content for the public (publis [...]
## Comparison with Sling Resource Merger
-In Sling Contrib a ["Apache Sling Resource
Merger"](https://github.com/apache/sling-org-apache-sling-resourcemerger)
bundle is provided. Although both Sling Resource Merger and the Superimposing
Resource Provider take care of mirroring and merging resources they solve quite
different problems and have different usecases:
+In Sling Contrib a [Apache Sling Resource
Merger](https://sling.apache.org/documentation/bundles/resource-merger.html)
bundle is provided. Although both Sling Resource Merger and the Superimposing
Resource Provider take care of mirroring and merging resources they solve quite
different problems and have different usecases:
* Sling Resource Merger is primary about Merging resources of content
structures from /apps and /libs, e.g. dialog definitions of an CMS application.
It mounts the merged resources at a new path (e.g. /mnt/overlay) which can be
included in the script resolution.
* The Superimposing Content Resource Provider is targeted at content. Think of
a scenario with one master site that is rolled out to hundreds of slave sites
with mostly identical contents but some site-specific overrides and
customizations. This is not possible with Sling Resource Merger and vice versa.
--
To stop receiving notification emails like this one, please contact
[email protected].
