You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ra...@apache.org on 2021/05/19 09:36:33 UTC
[sling-site] branch master updated: Fix small styling error and
link to the sling cheat-sheet
This is an automated email from the ASF dual-hosted git repository.
radu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/master by this push:
new f012118 Fix small styling error and link to the sling cheat-sheet
f012118 is described below
commit f012118498637206620ba7db94838dc30bf7f0e8
Author: Aravindo Wingeier <sy...@users.noreply.github.com>
AuthorDate: Wed May 19 11:36:27 2021 +0200
Fix small styling error and link to the sling cheat-sheet
Co-authored-by: Aravindo Wingeier <wi...@adobe.com>
---
src/main/jbake/content/documentation/bundles/osgi-installer.md | 1 +
.../documentation/the-sling-engine/mappings-for-resource-resolution.md | 1 +
.../content/documentation/the-sling-engine/sling-api-crud-support.md | 2 +-
.../jbake/content/documentation/the-sling-engine/url-decomposition.md | 2 +-
.../documentation/the-sling-engine/wrap-or-decorate-resources.md | 1 +
5 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/src/main/jbake/content/documentation/bundles/osgi-installer.md b/src/main/jbake/content/documentation/bundles/osgi-installer.md
index d807714..419101f 100644
--- a/src/main/jbake/content/documentation/bundles/osgi-installer.md
+++ b/src/main/jbake/content/documentation/bundles/osgi-installer.md
@@ -108,6 +108,7 @@ The OSGi installer provides a [Sling Health Check](/documentation/bundles/sling-
By default it will only check resources with a URL prefix `jcrinstall:/apps/`, so only the resources being provided through the [JCR Installer Provider](/documentation/bundles/jcr-installer-provider.html) initially located below the repository resource `/apps/` are considered.
The health check will fail in the following cases:
+
* Bundles Installation Failure
* Configuration Installation Failure
diff --git a/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md b/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
index 684eeed..69a1d5c 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/mappings-for-resource-resolution.md
@@ -250,6 +250,7 @@ The cache can be disabled by setting the property `resource.resolver.optimize.al
### Limitation of `sling:alias` for Principal with a limited access
Assuming there is
+
* An User named `testuser`
* An ACE with deny `jcr:all` in `/` for `everyone`
* An ACE with allow `jcr:read` in `/content` for `testuser`
diff --git a/src/main/jbake/content/documentation/the-sling-engine/sling-api-crud-support.md b/src/main/jbake/content/documentation/the-sling-engine/sling-api-crud-support.md
index eba4789..3d6fd1e 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/sling-api-crud-support.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/sling-api-crud-support.md
@@ -21,7 +21,7 @@ Which provide the ability to create and delete resources as well as the addition
## Comparing Sling API CRUD to Sling Post Servlet
-Here are some examples of common operations performed using the Sling Post Servlet and Sling API CRUD support. Note, the examples are derived from the [SlingPostServlet Cheatsheet](http://dev.day.com/content/ddc/blog/2008/07/cheatsheet/_jcr_content/images/cheatsheet/back.png).
+Here are some examples of common operations performed using the Sling Post Servlet and Sling API CRUD support. Note, the examples are derived from the cheat sheet in Adobe's AEM documentation at [https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/sling-cheatsheet.html](https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/sling-cheatsheet.html).
### Updating a Property
diff --git a/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md b/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
index 73bb073..84e2d97 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/url-decomposition.md
@@ -20,7 +20,7 @@ It is up to the [Resource Provider](resources.html#providing-resources) to decid
The decomposed parts can be accessed through the `RequestPathInfo` object, which is retrieved via [SlingHttpServletRequest.getPathInfo()](https://sling.apache.org/apidocs/sling7/org/apache/sling/api/SlingHttpServletRequest.html#getRequestPathInfo--).
-There's a cheat sheet in Adobe's AEM documentation at [https://docs.adobe.com/docs/en/aem/6-2/develop/platform/sling-cheatsheet.html](https://docs.adobe.com/docs/en/aem/6-2/develop/platform/sling-cheatsheet.html) available to get you familiar with the URL decomposition of Sling.
+There's a cheat sheet in Adobe's AEM documentation at [https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/sling-cheatsheet.html](https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/developing/full-stack/sling-cheatsheet.html) available to get you familiar with the URL decomposition of Sling.
# Examples #
Assume there is a Resource at `/a/b`, which has no children.
diff --git a/src/main/jbake/content/documentation/the-sling-engine/wrap-or-decorate-resources.md b/src/main/jbake/content/documentation/the-sling-engine/wrap-or-decorate-resources.md
index e948451..313de9e 100644
--- a/src/main/jbake/content/documentation/the-sling-engine/wrap-or-decorate-resources.md
+++ b/src/main/jbake/content/documentation/the-sling-engine/wrap-or-decorate-resources.md
@@ -7,6 +7,7 @@ tags=resources
## Introduction
The Sling API provides an easy way to wrap or decorate a resource before returning. Use cases for this could for example be
+
* overwrite resource type/resource super type (for example based on the resource path)
* add metadata