Radu Cotescu created SLING-6165:

             Summary: Expose a service for Sling Scripting that provides 
request-scoped Resource Resolvers for scripting dependencies
                 Key: SLING-6165
                 URL: https://issues.apache.org/jira/browse/SLING-6165
             Project: Sling
          Issue Type: New Feature
          Components: Scripting
            Reporter: Radu Cotescu
            Assignee: Radu Cotescu
             Fix For: Scripting Core 2.0.42, Scripting API 2.1.10

A new Sling Scripting service ({{ScriptingResourceResolverProvider}}) should be 
implemented in order to provide access to request-based {{ResourceResolvers}} 
for solving script dependencies.

The following two methods should be available:

 * Provides a request-scoped {@link ResourceResolver} with only read access to 
the search paths. This resolver should be used for script 
 * resolution in the context of the same request rendering process. The {@code 
ResourceResolver} should not be closed by consumers (calling
 * {@link ResourceResolver#close} doesn't do anything), since this service will 
handle the closing operation automatically. The 
 * {@code ResourceResolver} will be shared between scripting dependencies that 
render parts of the response for the same request.
ResourceResolver getRequestScopedResourceResolver()

 * Provides a {@link ResourceResolver} with only read access to the search 
paths. Once you're done processing {@link Resource}s with this 
 * {@code ResourceResolver} make sure to close it.
ResourceResolver getResourceResolver()

[sling-dev email 

This message was sent by Atlassian JIRA

Reply via email to