[
https://issues.apache.org/jira/browse/SOLR-15121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280224#comment-17280224
]
David Smiley commented on SOLR-15121:
-------------------------------------
I think returning to the old XsltResponseHandler is fine -- thus puts this
functionality at the handler level, which is a well supported existing pluging.
WDYT of that [~uschindler]?
Also, the last time I checked, we were including an XSLT engine (was it
Xalan?). I need to step AFK for now but let's not include it; maybe only in the
scripting contrib.
> 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: 2h 10m
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
