On Jun 15, 2006, at 10:18 AM, Yonik Seeley wrote:
On 6/15/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
Having a way to hook into the response writing by leveraging the ever
improving Solr codebase and its utilities rather than copy/pasting
would be a nice way to aim, I think.
It's a double edg
On 6/15/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
Having a way to hook into the response writing by leveraging the ever
improving Solr codebase and its utilities rather than copy/pasting
would be a nice way to aim, I think.
It's a double edged sword. Making more things public facilitates
reu
On Jun 15, 2006, at 3:37 AM, Chris Hostetter wrote:
: are linked to the one being written, think relationships here). I'm
: having difficulty customizing the output because XMLWriter's
: constructor is package protected. Is there a performance or API
: reason we need this class to be uninstant
: are linked to the one being written, think relationships here). I'm
: having difficulty customizing the output because XMLWriter's
: constructor is package protected. Is there a performance or API
: reason we need this class to be uninstantiable from other packages?
: Having it still final is o
