You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by jo...@apache.org on 2021/04/16 13:54:36 UTC
[sling-org-apache-sling-api] 01/01: SLING-10276 updated javadoc
This is an automated email from the ASF dual-hosted git repository.
joerghoh pushed a commit to branch feature/SLING-10276-updated-javadoc
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-api.git
commit aa640ade12d5e496b89bab3b38d6345eed9c63d1
Author: Joerg Hoh <jh...@adobe.com>
AuthorDate: Fri Apr 16 15:54:17 2021 +0200
SLING-10276 updated javadoc
---
.../java/org/apache/sling/api/resource/ResourceResolver.java | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/src/main/java/org/apache/sling/api/resource/ResourceResolver.java b/src/main/java/org/apache/sling/api/resource/ResourceResolver.java
index 8a2b27d..03dee38 100644
--- a/src/main/java/org/apache/sling/api/resource/ResourceResolver.java
+++ b/src/main/java/org/apache/sling/api/resource/ResourceResolver.java
@@ -103,6 +103,15 @@ import org.osgi.annotation.versioning.ProviderType;
* is more than one resource provider involved and one of them fails in persisting,
* changes already committed to other providers are not reverted.
* <p>
+ * <b>External changes</b>
+ * <p>
+ * Changes which happen outside of the Resource API provided by Sling are not required
+ * to be reflected immediately within an already opened ResourceResolver and its associated
+ * resources.
+ * For example, if the ResourceResolver is backed by a JCR implementation, any changes within
+ * the JCR session (which is an implementation detail of the respective ResourceResolver
+ * implementation) are not required to be reflected within its Resource Resolver.
+ * <p>
* <b>Lifecycle</b>
* <p>
* A Resource Resolver has a life cycle which begins with the creation of the