Re: URI Encoding with Solr and Weblogic

[Elisabeth Adler]

Hi,

I found a solution to it.
Adding the Weblogic Server Argument -Dfile.encoding=UTF-8 did not affect 
the encoding.

Only a change to the .war file's weblogic.xml and redeployment of the 
modified .war solved it.
I added the following to the weblogic.xml:

<charset-params>
  <input-charset>
    <resource-path>*</resource-path>
    <java-charset-name>UTF-8</java-charset-name>
  </input-charset>
</charset-params>

Would it make sense to include this in the shipped weblogic.xml file?

Best,
Elisabeth

On 07.02.2012 23:12, Elisabeth Adler wrote:
Hi,

I try to get Solr 3.3.0 to process Arabic search requests using its
admin interface. I have successfully managed to set it up on Tomcat
using the URIEncoding attribute but fail miserably on WebLogic 10.

Invoking the URL http://localhost:7012/solr/select/?q=تهنئة returns the
XML below:
<response>
<lst name="responseHeader">
<int name="status">0</int>
<int name="QTime">0</int>
<lst name="params">
<str name="q">تهنئة</str>
</lst>
</lst>
<result name="response" numFound="0" start="0"/>
</response>

The search term is just gibberish. Running the query through Luke or
Tomcat returns the expected result and renders the search term correctly.

I have tried to change the URI encoding and JVM default encoding by
setting the following start up arguments in WebLogic:
-Dfile.encoding=UTF-8 -Dweblogic.http.URIDecodeEncoding=UTF-8. I can see
them being set through Solr's admin interface. They don't have any
impact though.

I am running out of ideas on how to get this working. Any thoughts and
pointers are much appreciated.

Thanks,
Elisabeth