I'm trying to take advantage of the Solr 1.4 Xinclude feature to
include a different xml fragment (e.g. a different analyzer chain in
schema.xml) for each core in a multi-core setup. When the Xinclude
operates on a relative path, it seems to NOT be acting relative to the
xml file with the Xinlclude statement. Using the jetty example, it
looks for a file in example/.
Is this a bug in the way Solr invokes Xinclude? If not, is there a
variable that contains the instanceDir that can be used?
${solr.instanceDir} or ${solr/instanceDir}
DOMUtil.substituteProperties(doc, loader.getCoreProperties());
I see that I could potentially specify solrcore.properties,
http://wiki.apache.org/solr/SolrConfigXml#System_property_substitutionin
order to determine the correct based path, but this seems overly
complicated in terms of wht the useual use case would be for Xinclude?
-Peter
--
Peter M. Wolanin, Ph.D.
Momentum Specialist, Acquia. Inc.
peter.wola...@acquia.com
