lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Dyer (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (SOLR-1226) XPathEntityProcessor should resolve xsl references within Solr's configuration
Date Wed, 28 Mar 2012 18:39:29 GMT


James Dyer resolved SOLR-1226.

       Resolution: Won't Fix
    Fix Version/s:     (was: 4.0)
         Assignee:     (was: Noble Paul)

The "threads" feature was removed from DIH in Trunk/4.x (see SOLR-3262). Some "threads" bugs
were fixed in version 3.6, the last release in which "threads" is available. (see SOLR-3011).
> XPathEntityProcessor should resolve xsl references within Solr's configuration
> ------------------------------------------------------------------------------
>                 Key: SOLR-1226
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - DataImportHandler
>    Affects Versions: 1.4
>            Reporter: David Smiley
>            Priority: Minor
>         Attachments: SOLR-1226.patch
> The XPathEntityProcessor forces me to use a URL to specify where my XSL file is.  if
it is not a URL, what it should do is attempt to resolve it from Solr's configuration  via
SolrCore.getREsourceLoader().  I have attached a patch which does this.
> Note: it is not clear in the DIH what the concurrency model is and thus I was not certain
that XPathEntityProcessor needs to be thread-safe or not.  So just in case I cached the XSLT
Transformer in a thread-safe manner using a ThreadLocal.  If DIH committers know that it doesn't
have to be thread-safe then some of this code can be simplified.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message