Hi Thanks for your reply. In actual fact, the "config.aspx" will either return a valid xml, or it will return an empty string - and unfortunately an empty string is not considered valid xml by the Solr xml parser.
The "config.aspx" is a rather general application, returning all sorts of data, depending on the parameters supplied to it. It doesn't know what fallback xml is appropriate in a specific instance. For example, it might be called like this: http://localhost/config/config.aspx?id=core1dismax&weight=qf But if configuration in solrconfig.xml is entered incorrectly (eg maybe the "id" parameter to config.aspx is incorrect) then config.aspx returns an empty string. Other xml parsers which handle x:include, and xi:fallback, actually invoke the fallback if any error occurs during the include (not only if the include resource does not exist). Is it possible to configure the Solr parser so it invokes the fallback on any error? Thanks, Peter ________________________________________ From: Stefan Matheis [matheis.ste...@googlemail.com] Sent: Wednesday, 20 October 2010 22:05 To: solr-user@lucene.apache.org Subject: Re: xi:include Wouldn't it be easier to ensure, that your config.aspx returns valid xml? Wrap your existing Code with some Exception-Handling and return your fallback-xml if something goes wrong?
