[
https://issues.apache.org/jira/browse/SOLR-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999262#comment-12999262
]
Uwe Schindler commented on SOLR-1656:
-------------------------------------
My last comment simply means, that enabling XInclude for ConfigParsers that
work on InputStreams is broken (e.g. when a request comes in from network via
http) because no SystemID. I simply want to change the code to disable xinclude
for those parsers.
I will work on my patch today and look for other parts in Solr where XInclude
is used or complex XML files that support href-like. One example is DIH, which
config file supports xinclude but has the same problem. Also XSLs loaded by xml
response writer should use the custom EnityResolver.
I will also make the patch almost backwards compatible.
I will talk with Robert about including into 3.1, I don't see a problem.
> XInclude's are resolved relative CWD, not instance dir
> ------------------------------------------------------
>
> Key: SOLR-1656
> URL: https://issues.apache.org/jira/browse/SOLR-1656
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Hoss Man
> Attachments: SOLR-1656-mockup.patch,
> SOLR-1656_Support_SAX_SystemId_via_wrapping_InputStream.patch,
> Support_SAX_SystemId_via_wrapping_InputStream.patch
>
>
> As noted on the mailing list, when an XInclude in a config files refrences a
> relative path, it's resolved relative the CWD of the servlet container, and
> not the instanceDir of the core...
>
> http://old.nabble.com/using-Xinclude-with-multi-core-to26548400.html#a26548400
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
