Oh,I am sorry, Ryan, I am afriad I made a mistake.
It doesn't work yet.When I deploy the new war, it looks like before.
I rewrite to "IOUtils.copy( content.getStream(), writer, "utf-8" )" and it
works fine again!
It wroks, and a request with
argument "&contentType=text/xml;charset=utf-8" required to show my CJK
characters in my config file.
Thanks, Ryan
On 3/7/08, Ryan McKinley <[EMAIL PROTECTED]> wrote:
>
> Thanks for pointing this out.
>
> In trunk, I changed the RawResponseWriter to use the Reader rat
Thanks for pointing this out.
In trunk, I changed the RawResponseWriter to use the Reader rather then
the Stream -- this way, you should not have to specify the contentType
to make it match the FileReader.
Does this fix your issues?
thanks
ryan
Edward Zhang wrote:
> My workmate and me found a
My workmate and me found a solution to this problem: it caused by
org.apache.solr.request.RawResponseWriter.
Solr required the config file encoded in UTF-8 by far. But when
RawResponseWriter put the byte stream to writer, it doesn't notice the
characters encoding.There may be some trouble when the
