The response writers print a debug message when you put a non-standard
value in them:
} else {
// default... for debugging only
writeStr(name, val.getClass().getName() + ':' + val.toString(), true);
}
All the values used in the standard handlers are in the list, so this
is fine.
On 3/3/07 1:43 PM, "Chris Hostetter" <[EMAIL PROTECTED]> wrote:
> : Right now, Solr accesses the DOM as needed (at runtime) to fetch
> : information. There isn't much up-front checking beyond the XML
> : parser.
>
> bingo, and adding more upfront checking is hard for at least two reasons i
> can
: All the values used in the standard handlers are in the list, so this
: is fine. I'm writing some custom handlers where it would be nice to
: put an arbitrary object into the response and have it printed out with
: toString()
Keep in mind, there is a contract about what constitutes "Returnable
Keep in mind, there is a contract about what constitutes "Returnable data"
http://lucene.apache.org/solr/api/org/apache/solr/request/SolrQueryResponse.html#returnable_data
That list is not quite up-to-date, it should add:
* Document
* Collection should be changed to: Iterable
* Iterator
.
On 3/4/07, Ryan McKinley <[EMAIL PROTECTED]> wrote:
Yes, i could figure some other way to do this, but mostly I was
surprised that the writers default to a debugging action rather then a
useful one.
It was useful to me at the time to try and figure out if I had
everything in the list I needed ;
: That list is not quite up-to-date, it should add:
:
: * Document
Really? ... i guess i missed that one (i thought it had to be in a
DocList)
: * Collection should be changed to: Iterable
: * Iterator
Collection changed to Iterable i remember (that was totally backwards
compatably) adding
:
: > : 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.
: T
On 3/4/07 3:01 PM, "Chris Hostetter" <[EMAIL PROTECTED]> wrote:
> 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 e
