[jira] [Updated] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies
[ https://issues.apache.org/jira/browse/SLING-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6165: Fix Version/s: (was: Scripting Core 2.0.42) (was: Scripting API 2.1.10) > 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 API 2.1.12, Scripting Core 2.0.44 > > > 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: > {noformat} > /** > * 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() > {noformat} > [sling-dev email > thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies
[ https://issues.apache.org/jira/browse/SLING-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6165: Fix Version/s: Scripting Core 2.0.44 Scripting API 2.1.12 > 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 API 2.1.12, Scripting Core 2.0.44 > > > 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: > {noformat} > /** > * 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() > {noformat} > [sling-dev email > thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies
[ https://issues.apache.org/jira/browse/SLING-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6165: 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: {noformat} /** * 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() {noformat} [sling-dev email thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] was: A new Sling Scripting service ({{ScriptingResourceResolverFactory}}) should be implemented in order to provide access to request-based {{ResourceResolvers}} for solving script dependencies. The following two methods should be available: {noformat} /** * 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() {noformat} [sling-dev email thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] > 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 method should be available: > {noformat} > /** > * 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() > {noformat} > [sling-dev email > thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies
[ https://issues.apache.org/jira/browse/SLING-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6165: Description: A new Sling Scripting service ({{ScriptingResourceResolverFactory}}) should be implemented in order to provide access to request-based {{ResourceResolvers}} for solving script dependencies. The following two methods should be available: {noformat} /** * 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() {noformat} [sling-dev email thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] was: 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: {noformat} /** * 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() {noformat} [sling-dev email thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] > 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 ({{ScriptingResourceResolverFactory}}) should > be implemented in order to provide access to request-based > {{ResourceResolvers}} for solving script dependencies. > The following two methods should be available: > {noformat} > /** > * 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() > {noformat} > [sling-dev email > thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-6165) Expose a service for Sling Scripting that provides request-scoped Resource Resolvers for scripting dependencies
[ https://issues.apache.org/jira/browse/SLING-6165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6165: 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 two methods should be available: {noformat} /** * 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() {noformat} [sling-dev email thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] was: 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: {code:java} /** * 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() {code} [sling-dev email thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] > 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 API 2.1.10, Scripting Core 2.0.42 > > > 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: > {noformat} > /** > * 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() > {noformat} > [sling-dev email > thread|https://lists.apache.org/thread.html/db2a78249baf2d6234a4549a5aff8b5474256add9829f86ac78d1c56@%3Cdev.sling.apache.org%3E] -- This message was sent by Atlassian JIRA (v6.3.4#6332)