Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: domain of richmondmike@gmail.com
 designates 66.249.92.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=djB64ohHedOi8fbdsB9sam7yg9w8nXMfN2KtMjYWLnEe8uSdLAsqzujV9azvtxd6SUyN8S6ynz8LsVFEFKNirqaN0GXKOXf4DyCksPMCm5CKY6402XW4RcmLpthfkobC07wmd5/PjekHkZL7NKkrdlsMjmLusQtGcXMAUFYMKFY=
Message-ID: <931ca11b0606200835q6d05e91dx599f215d9b8c690d@mail.gmail.com>
Date: Tue, 20 Jun 2006 11:35:05 -0400
From: "Mike Richmond" <richmondmike@gmail.com>
To: solr-user@lucene.apache.org
Subject: Re: Invalid XML returned from Solr
In-Reply-To: <c68e39170606200829o3f9fefb6u89e6d16a5055e679@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <931ca11b0606200804u7b6d9906u23068fe4db0e2745@mail.gmail.com>
	 <c68e39170606200829o3f9fefb6u89e6d16a5055e679@mail.gmail.com>

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 into giving Tomcat a try over Jetty.


--Mike


On 6/20/06, Yonik Seeley <yseeley@gmail.com> wrote:
> On 6/20/06, Mike Richmond <richmondmike@gmail.com> 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 substitution).  In particular the
> > "summary" field contains '<' characters. An example of such a response
> > can be found here: http://www.willetts.com/mike/response.xml
>
> Hmmm, that is interesting... I haven't seen that before.
> I'll try and duplicate it with your example "summary" field.
>
> > On another note:
> > I also noticed that I get non-utf8 characters in the response even
> > though the encoding line at the top of the XML document specifies utf8
> > encoding.
>
> Are you using the bundled version of Jetty?  People have been having
> problems with international chars with that.  You might try using
> Tomcat.
>
> > I did not see anywhere in the XMLWriter code that checked
> > the encoding of the output.  Is this by design, or am I missing
> > something?
>
> By design... XMLWriter writes java characters and strings, and the
> servlet container handles encoding to UTF-8.
>
> -Yonik
>