Author: cziegeler Date: Wed Apr 21 08:34:51 2010 New Revision: 936201 URL: http://svn.apache.org/viewvc?rev=936201&view=rev Log: Clarify javadoc
Modified: sling/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java Modified: sling/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java URL: http://svn.apache.org/viewvc/sling/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java?rev=936201&r1=936200&r2=936201&view=diff ============================================================================== --- sling/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java (original) +++ sling/trunk/bundles/api/src/main/java/org/apache/sling/api/resource/ResourceResolver.java Wed Apr 21 08:34:51 2010 @@ -36,6 +36,12 @@ import org.apache.sling.api.adapter.Adap * adapters to other types. A JCR based resource resolver might support adapting * to the JCR Session used by the resolver to access the JCR Repository. * <p> + * A <code>ResourceResolver</code> is generally not thread safe! As a consequence, + * an application which uses the resolver, its returned resources and/or objects + * resulting from adapting either the resolver or a resource, must provide + * proper synchronization to ensure no more than one thread concurrently operates + * against a single resolver, resource or resulting objects. + * <p> * This interface defines two kinds of methods to access resources: The * <code>resolve</code> methods and the <code>getResource</code> methods. The * difference lies in the algorithm applied to find the requested resource and