Hi Yonik,
Thanks again for the quick help. I switched to Tomcat and all the
problems went away.
Not sure what the process would be but I'd be willing to migrate the
example application to tomcat and update the existing documentation.
I would like to give back to this project as it has done quit
I've confirmed this is a Jetty bug related to international chars
(>=128) and their output writer. When I moved the example to Tomcat
5.5, everything worked as expected.
For the exact same Lucene index file,
Tomcat outputs
I¹ll
and Jetty outputs
I¹ll
We should really look into
Hi Yonik,
Thanks for the quick reply. I am willing to give you access to my
index, config files, or any other pieces that you may need if it would
help. I am basically running the example application (which uses
Jetty), but with a modified schema.xml and a couple other small
changes.
I'll look
On 6/20/06, Mike Richmond <[EMAIL PROTECTED]> wrote:
I have a application that I recently ported to Solr and am running
into a few problems with the XML responses from Solr. An XML response
which came from a Solr query, returned XML data that was not properly
escaped (no CDATA tag, or entity sub