[jira] [Commented] (SLING-4931) Allow the script cache to observe other paths than search paths
[
https://issues.apache.org/jira/browse/SLING-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14661651#comment-14661651
]
Radu Cotescu commented on SLING-4931:
-
I'm referring to scripts handled by {{javax.script.ScriptEngine}}s, like the
ECMA scripts from CQ's workflow engine.
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)
[jira] [Commented] (SLING-4931) Allow the script cache to observe other paths than search paths
[ https://issues.apache.org/jira/browse/SLING-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14661648#comment-14661648 ] Bertrand Delacretaz commented on SLING-4931: Scripts outside of search paths sounds scary, all executable scripts should be under well specified paths for security reasons - can you elaborate? 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)
[jira] [Commented] (SLING-4931) Allow the script cache to observe other paths than search paths
[ https://issues.apache.org/jira/browse/SLING-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14661654#comment-14661654 ] Bertrand Delacretaz commented on SLING-4931: Ah ok makes sense, thanks for clarifying. 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)
[jira] [Commented] (SLING-4931) Allow the script cache to observe other paths than search paths
[
https://issues.apache.org/jira/browse/SLING-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (SLING-4931) Allow the script cache to observe other paths than search paths
[ https://issues.apache.org/jira/browse/SLING-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14661794#comment-14661794 ] Bertrand Delacretaz commented on SLING-4931: Actually I think you can create a SlingScript from any resource, whatever its path - so we don't currently have a limitation on where scripts can be executed from. I agree that it's best not to implement what was suggested here, but if we really want to limit where scripts come from we need other changes. 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)
