You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Oliver Lietz (Jira)" <ji...@apache.org> on 2021/06/02 16:07:00 UTC

[jira] [Commented] (SLING-10448) The Java Script Engine is not made available any more

    [ https://issues.apache.org/jira/browse/SLING-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355829#comment-17355829 ] 

Oliver Lietz commented on SLING-10448:
--------------------------------------

This [change|https://github.com/apache/sling-org-apache-sling-scripting-java/commit/4abea89#diff-060eb53d0a7e4c7f1779d81228da83d4f387f9b402eeb9ad4181d659b18fda67L68] will break the filtering on component properties.

> The Java Script Engine is not made available any more
> -----------------------------------------------------
>
>                 Key: SLING-10448
>                 URL: https://issues.apache.org/jira/browse/SLING-10448
>             Project: Sling
>          Issue Type: Bug
>          Components: Scripting
>    Affects Versions: Scripting Java 2.1.2
>            Reporter: Radu Cotescu
>            Assignee: Radu Cotescu
>            Priority: Major
>             Fix For: Scripting Java Support 2.1.4
>
>
> Starting with SLING-10155, it seems that the Java Script Engine, provided by the Apache Sling Scripting Java Support bundle, is not made available to the platform any more.
> This happens because the implementation of the Java Script Engine Factory doesn't correctly return the short names under which the script engine is made available.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)