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
On Jun 15, 2006, at 10:18 AM, Yonik Seeley wrote:
On 6/15/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
Having a way to hook into the response writing by leveraging the ever
improving Solr codebase and its utilities rather than copy/pasting
would be a nice way to aim, I think.
It's a double edg
It sounds like many people (myself included) try to avoid using yet another
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
pro
I'll be giving a Solr presentation at ApacheCon EU shortly.
If there is anyone who is using Solr and wants their company/site
mentioned in the presentation, let me know.
You can also update http://wiki.apache.org/solr/PublicServers if you like.
-Yonik
My Solr application is literally a week or less away from public
deployment. It's the Google/del.icious(ok, ok, Simpy!)/Flickr of
19th century literature. It's working very nicely as a Ruby on Rails
front-end with a bit of AJAX coolness for Google-suggest like
behavior (with the data comi
: 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
I'll be giving a Solr presentation at ApacheCon EU shortly.
If there is anyone who is using Solr and wants their company/site
mentioned in the presentation, let me know.
Just a general notice that http://krugle.com uses Solr to search
project data, and also to store an index to user-generated n
