[
https://issues.apache.org/jira/browse/JENA-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308993#comment-17308993
]
ASF subversion and git services commented on JENA-1951:
-------------------------------------------------------
Commit 12c8519c04e527d75c8eacd22e62abd4505a3f43 in jena's branch
refs/heads/main from Andy Seaborne
[ https://gitbox.apache.org/repos/asf?p=jena.git;h=12c8519 ]
Merge pull request #967 from afs/multilang
JENA-1951: Finish merge; remove legacy; adjust for RDF-star
> Add support for scripting languages other than JavaScript
> ---------------------------------------------------------
>
> Key: JENA-1951
> URL: https://issues.apache.org/jira/browse/JENA-1951
> Project: Apache Jena
> Issue Type: Task
> Components: ARQ
> Reporter: Pavel Mikhailovskii
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It's already possible to use user-defined JavaScript functions in SPARQL
> queries. This feature can be extended to support all scripting languages
> available via generic Java Scripting API (JSR-223). This would require a
> generic way of configuring scripting engines and accessing functions defined
> in them, potentially allowing mixing functions defined in different languages
> in one SPARQL query. Besides the GraalVM-powered JavaScript engine (see
> [JENA-1950|https://issues.apache.org/jira/browse/JENA-1950]) none of
> scripting engines will be bundled by default. They can be enabled by simply
> adding the corresponding packages to the class path.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
