Author: kwin
Date: Thu May 21 08:34:46 2015
New Revision: 1680763

URL: http://svn.apache.org/r1680763
Log:
create link to mailing list discussion around limitations on the sling objects 
injector

Modified:
    sling/site/trunk/content/documentation/bundles/models.mdtext

Modified: sling/site/trunk/content/documentation/bundles/models.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/models.mdtext?rev=1680763&r1=1680762&r2=1680763&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/models.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/models.mdtext Thu May 21 
08:34:46 2015
@@ -369,7 +369,7 @@ Request Attributes | `request-attributes
 OSGi Services      | `osgi-services`         | 5000                | 1.0.0     
                               | Lookup services based on class name | Any 
object | yes | yes | Parameterized `List` and `Collection` injection points are 
injected by getting an array of the services and creating an unmodifiable 
`List` from the array.
 Resource Path      | `resource-path`         | 2500                | 1.1.0     
                               | Injects a resource by its path. | `Resource` 
or `SlingHttpServletRequest` objects | yes | none | none
 Self               | `self`                  | `Integer.MAX_VALUE` | 1.1.0     
                               | Injects the adaptable object itself (if the 
class of the field matches or is a supertype). If the @Self annotation is 
present it is tried to adapt the adaptable to the field type.  | Any object | 
yes | none | none
-Sling Object       | `sling-object`          | `Integer.MAX_VALUE` | 1.1.0     
                               | 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 
`SlingHttpServletRequest` while `ResourceResolver` can only resolve the 
`ResourceResolver` object and nothing else | `Resource`, `ResourceResolver` or 
`SlingHttpServletRequest` objects | yes | none | none
+Sling Object       | `sling-object`          | `Integer.MAX_VALUE` | 1.1.0     
                               | 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 
`SlingHttpServletRequest` while `ResourceResolver` can only resolve the 
`ResourceResolver` object and nothing else. A discussion around this limitation 
and a potential solution can be found at the [sling-dev mailing 
list](http://apache-sling.73963.n3.nabble.com/RTC-ThreadLocal-for-getting-current-request-in-sling-td4042387.html).
 | `Resource`, `ResourceResolver` or `SlingHttpServletRequest` objects (not all 
objects can be resolved by all adaptables) | yes | none | none
 
 # Injector-specific Annotations (Since Sling Models Impl 1.0.6)
 


Reply via email to