You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Radu Cotescu (JIRA)" <ji...@apache.org> on 2019/05/22 14:39:00 UTC

[jira] [Resolved] (SLING-8431) On Java 11 the platform provided script engine factories might be registered more than once

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

Radu Cotescu resolved SLING-8431.
---------------------------------
    Resolution: Fixed

Fixed in [commit cdec524|https://github.com/apache/sling-org-apache-sling-scripting-core/commit/cdec524].

> On Java 11 the platform provided script engine factories might be registered more than once
> -------------------------------------------------------------------------------------------
>
>                 Key: SLING-8431
>                 URL: https://issues.apache.org/jira/browse/SLING-8431
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Core 2.0.52
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting Core 2.0.58
>
>
> When running on Java 11 and deploying bundles providing SPI Script Engine Factories platform provided script engine factories might be registered more than once. This is evidenced by the failure of the {{org.apache.sling.scripting.core.impl.jsr223.SlingScriptEngineManagerTest#testBundledScriptEngineFactory}} test.
> This happens because the bundle class loader used for the service loader through which SPI Script Engine Factories are loaded also provides the platform provided factories. The solution would be to make sure that the generated {{SortableScriptinEngineFactories}} are added to the internal set only if they rely on different delegate factories.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)