FYI: The Tomcat UTF-8 problem and the extra configuration needed because of that is no longer a problem since I fixed the URL-Decoding to be handled by Solr’s dispatch filter. The servlet container is out of responsibility, it just have to provide the query string or ServletInputStream (depends on GET/POST). Example/test_utf8.sh works out of the box with Tomcat or JBoss.
Nevertheless I would also tend to no longer publish a WAR. ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: [email protected] From: Robert Muir [mailto:[email protected]] Sent: Friday, May 03, 2013 4:43 PM To: [email protected] Subject: Re: VOTE: solr no longer webapp On Thu, May 2, 2013 at 9:40 PM, Walter Underwood <[email protected]> wrote: -1 We run everything under Tomcat. This would be a big, unnecessary hassle for ops and an obstacle to adoption. I don't intend for my vote to be popular with users, instead for this to be a developer vote. Users will rarely vote in favor the removal of a "feature" (in this case the .war "feature"), but sometimes it is a necessary thing to do. In the case of no longer supporting tomcat: this is an extremely useful feature in itself. "not using tomcat" == utf-8 working out of box, threadpools with reasonable defaults configured out of box, tested configuration executed in open source unit tests, ... I cannot understand why anyone would want to use tomcat. There is no possible reason to justify such a bad decision.
