You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2023/04/12 07:22:00 UTC

[jira] [Resolved] (SLING-841) Set thread context class loader on behalf of script engines

     [ https://issues.apache.org/jira/browse/SLING-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-841.
------------------------------------
    Resolution: Won't Fix

> Set thread context class loader on behalf of script engines
> -----------------------------------------------------------
>
>                 Key: SLING-841
>                 URL: https://issues.apache.org/jira/browse/SLING-841
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>    Affects Versions: Scripting Core 2.0.2
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>            Priority: Major
>
> Often times script engines might expect the thread class loader to be set to the correct instance. Most notably if any scripts are using JAXP, setting the thread context class loader correctly is crucial to executing the script correctly.
> One solution would be to delegate setting the contetx class loader to the script engine. Since this is a common task, I would argue, that the thread context class loader should be set by the scripting core module, which calls into the script engines.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)