You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2015/05/21 10:34:53 UTC
svn commit: r952160 - in /websites/staging/sling/trunk/content: ./
documentation/bundles/models.html
Author: buildbot
Date: Thu May 21 08:34:53 2015
New Revision: 952160
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/bundles/models.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu May 21 08:34:53 2015
@@ -1 +1 @@
-1680762
+1680763
Modified: websites/staging/sling/trunk/content/documentation/bundles/models.html
==============================================================================
--- websites/staging/sling/trunk/content/documentation/bundles/models.html (original)
+++ websites/staging/sling/trunk/content/documentation/bundles/models.html Thu May 21 08:34:53 2015
@@ -580,8 +580,8 @@ Validation is only supported on models w
<td><code>sling-object</code></td>
<td><code>Integer.MAX_VALUE</code></td>
<td>1.1.0</td>
-<td>Injects commonly used sling objects if the field matches with the class: request, response, resource resolver, current resource, SlingScriptHelper. This works only if the adaptable can get the according information, i.e. all objects are available via <code>SlingHttpServletRequest</code> while <code>ResourceResolver</code> can only resolve the <code>ResourceResolver</code> object and nothing else</td>
-<td><code>Resource</code>, <code>ResourceResolver</code> or <code>SlingHttpServletRequest</code> objects</td>
+<td>Injects commonly used sling objects if the field matches with the class: request, response, resource resolver, current resource, SlingScriptHelper. This works only if the adaptable can get the according information, i.e. all objects are available via <code>SlingHttpServletRequest</code> while <code>ResourceResolver</code> can only resolve the <code>ResourceResolver</code> object and nothing else. A discussion around this limitation and a potential solution can be found at the <a href="http://apache-sling.73963.n3.nabble.com/RTC-ThreadLocal-for-getting-current-request-in-sling-td4042387.html">sling-dev mailing list</a>.</td>
+<td><code>Resource</code>, <code>ResourceResolver</code> or <code>SlingHttpServletRequest</code> objects (not all objects can be resolved by all adaptables)</td>
<td>yes</td>
<td>none</td>
<td>none</td>
@@ -678,7 +678,7 @@ SPI interface which could use context to
content path context. If multiple implementations of the <code>ImplementationPicker</code> interface are present, they are queried
one after another in order of their service ranking property, the first one that picks an implementation wins.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
- Rev. 1680762 by kwin on Thu, 21 May 2015 08:25:05 +0000
+ Rev. 1680763 by kwin on Thu, 21 May 2015 08:34:46 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project