You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Uwe Schindler (Jira)" <ji...@apache.org> on 2021/02/06 12:07:00 UTC
[jira] [Comment Edited] (SOLR-15121) Move XSLT (tr param) to
scripting contrib
[ https://issues.apache.org/jira/browse/SOLR-15121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280168#comment-17280168 ]
Uwe Schindler edited comment on SOLR-15121 at 2/6/21, 12:06 PM:
----------------------------------------------------------------
The XML APIs in Java are so great to have those pluggable transformations, so let's use those. I wrote many frameworks doing this (in library world where I am coming from, everything is XML, so you have partially really long chains of handlers feeding some DOM trees / other representations) from one handler to the other (I also managed to use XSL to convert XML to JSON to provide schema.org from our library XML OAI metadata). So adding some abstract "transform" hook into Solr core makes pluggable transformations easy.
So in general I would revert the whole stuff, make the transformation in core a protected method and in contrib implement one "example" implementation of XML transformations - using XSLT.
was (Author: thetaphi):
The XML APIs in Java are so great to have those pluggable transformations, so let's use those. I wrote many frameworks doing this (in library world where I am comoning from everything is XML, so you have partially really long chains of handlers feeding some DOM trees / other representations) from one handler to the other. So adding some abstract "transform" hook into Solr core makes pluggable transformations easy.
So in general I would revert the whole stuff, make the transformation in core a protected method and in contrib implement one "example" implementation of XML transformations - using XSLT.
> Move XSLT (tr param) to scripting contrib
> -----------------------------------------
>
> Key: SOLR-15121
> URL: https://issues.apache.org/jira/browse/SOLR-15121
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Eric Pugh
> Priority: Blocker
> Fix For: master (9.0)
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The XSLT functionality, present in both XML /update loading, and also in the response writer, ought to move to the "scripting" contrib module because XSLT is a type of scripting. XSLT is risky from a security standpoint, and so should not be in solr-core.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org