: application server (Tomcat) initially. While I think it's already been
: alluded to pretty well, it might be a good idea to stress on the Solr wiki
: that the Jetty instance isn't fully debugged and is only recommended for
: proof-of-concept.
I think the goal was to avoid advocating for or aga
mended for
proof-of-concept.
-Original Message-
From: Fabio Confalonieri [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 3:55 AM
To: solr-user@lucene.apache.org
Subject: Re: International Charsets in embedded XML
Ok, I fould de clue:
the problem is Jetty, using Tomcat everything work
Ok, I fould de clue:
the problem is Jetty, using Tomcat everything works fine.
I can search diacritics (I found Jetty required an extra UTF8 encoding on
query values in the url)
AND
no more problems in responses with field containing XML with diacritics and
Euro sign (and everything else I suppos
Ok, thanks to Your posts, I've read some basic on encoding and made some
changes to my code: now it's all much more clear... but I still have some
problems.
This is what I do (don't know if this can help someone having same problems
I had):
- I get data from a DB telling JDBC connector to use UT
On 6/13/06, Fabio Confalonieri <[EMAIL PROTECTED]> wrote:
Klaas-2 wrote:
> Are you sending Content-Type headers with appropriate charset
> indicated? Is your xml fully-escpaed in your update message?
...no, actually I simply make a
URLConnection conn = url.openConnect
Klaas-2 wrote:
Are you sending Content-Type headers with appropriate charset
indicated? Is your xml fully-escpaed in your update message?
...no, actually I simply make a
URLConnection conn = url.openConnection();
conn.setRequestProperty("Con
Klaas-2 wrote:
>
> Are you sending Content-Type headers with appropriate charset
> indicated? Is your xml fully-escpaed in your update message?
>
...no, actually I simply make a
URLConnection conn = url.openConnection();
conn.setRequestProperty
On 6/13/06, Fabio Confalonieri <[EMAIL PROTECTED]> wrote:
(sorry the last one got wrongly posted)
Are you sending Content-Type headers with appropriate charset
indicated? Is your xml fully-escpaed in your update message?
-Mike
