[
https://issues.apache.org/jira/browse/SLING-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661792#comment-14661792
]
Radu Cotescu commented on SLING-4931:
-------------------------------------
Probably because people were not considerate when they implemented this
functionality a few years ago. However I figured out that the core issue can be
fixed locally, without having to modify the Script Cache's Event Handler.
Sling itself doesn't enforce from what kind of resources a {{SlingScript}} can
be obtained. Therefore you could create a {{SlingScript}} with a fake resource,
because the {{SlingScriptAdapterFactory}} doesn't check a resource's path
against the configured search paths.
> Allow the script cache to observe other paths than search paths
> ---------------------------------------------------------------
>
> Key: SLING-4931
> URL: https://issues.apache.org/jira/browse/SLING-4931
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting Core 2.0.32
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Fix For: Scripting Core 2.0.34
>
>
> There are cases when a script resides outside of search paths, in which case
> custom locations should be allowed to be added to the Script Cache Event
> Handler implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
