[SLING-6165] Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Scripting Core 2.0.44, Scripting API 2.1.12
• Component/s: Scripting
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 17/Oct/16 09:49
• Updated: 15/Dec/16 13:02
• Resolved: 30/Nov/16 08:06

Description

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

The following method 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()

sling-dev email thread

Issue Links

• blocks: SLING-6166 Update the HTL bundles to use the SLING-6165 request-scoped resource resolver
• blocks: SLING-5928 Use Service ResourceResolver in SlingResourceTemplateResolver
• is blocked by: SLING-6336 Implement a ResourceResolverWrapper