sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Peltier (Jira)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7772) add other scripting options for pipe expressions
Date Tue, 30 Jun 2020 13:19:00 GMT

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

Nicolas Peltier commented on SLING-7772:
----------------------------------------

ho [~bdelacretaz] just saw your comment, so yeah, using embedded JEXL finally as i was too
lazy to implement my own :) and yes, it's possible to use whatever "external" scripting engine
by adding "engine" binding or property to the pipe. Your proposal of one engine per expression
is interesting but will not be implemented yet :) initializing an engine each time with context
will (i think) take time.

> add other scripting options for pipe expressions
> ------------------------------------------------
>
>                 Key: SLING-7772
>                 URL: https://issues.apache.org/jira/browse/SLING-7772
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions, pipes
>    Affects Versions: Pipes 2.0.2
>            Reporter: Nicolas Peltier
>            Priority: Major
>             Fix For: Pipes 3.2.0
>
>
> nashorn is being deprecated (http://openjdk.java.net/jeps/335). There might be another
option soon, that will be another dependency.
> Thinking about it, we should provide an option for script in pipe expression (which should
be fairly easy to do). And may be thinking of changing the default script engine not to be
JS anymore but something that does not need dependency installed, popular and performant



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

Mime
View raw message