: : > : Right now, Solr accesses the DOM as needed (at runtime) to fetch : > : information. There isn't much up-front checking beyond the XML : > : parser.
: I was thinking of translating the config file into internal config : properties when it was read, and logging Solr specific errors then. : Things like "I can't load this class" are pretty easy at that poin. most of that work is done right now when the solrconfig.xml and schema.xml are loaded ... any missing classes should be logged as errors immediately. I'm actaully haven't a hard time thinking of what kinds of "just in time" DOM walking is delayed until request ... all of the feld names are already known, the analyzers are built, the requesthandlers and responsewriters all exist and have been initialized ... what stuff isn't checked until a request comes in? -Hoss
