[
https://issues.apache.org/jira/browse/SOLR-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989737#comment-13989737
]
David Smiley commented on SOLR-6042:
------------------------------------
Ah; I forgot about entities; and the link at Mapnik was interesting. Uwe, in
your opinion, would this issue still be useful?
> Allow XInclude'ed config to have a top level <INCLUDE> which gets stripped
> --------------------------------------------------------------------------
>
> Key: SOLR-6042
> URL: https://issues.apache.org/jira/browse/SOLR-6042
> Project: Solr
> Issue Type: Improvement
> Reporter: David Smiley
> Priority: Minor
>
> The XInclude feature is pretty cool but it's limited to including a
> configuration element that has one top level tag. For example "<types>".
> That's a big limitation. This issue proposes that a special XML element of
> the name "INCLUDE" (or whatever) be allowed in a config file, which is
> stripped out when Solr reads the file. Solr would recursively check for
> elements of this name and if found then replace the node with all its
> children. In practice, nobody would use this except as a root of an
> XInclude'ed configuration fragment.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
