> My organization has issues with Jetty (some customers don't want Jetty on > their boxes, but are OK with WebSphere or Tomcat) so I'm trying to figure > out: how to get Solr on WebSphere / Tomcat without using WAR knowing that > the WAR will go away.
I understand that some customers are irrational. Doesn't mean you (or Solr) should cater to them. I've heard the objections, and they're all nonsense. Jetty is slow? WebSphere is easier to manage? Tomcat doesn't support X/Y/Z. It's all nonsense. We're currently in the process of migrating our applications away from WARs for many of the same reason as Solr. Whether or not we use Jetty internally to handle HTTP requests isn't anyone's concern. The best way to explain it to your irrational customers is that you're running Solr, instead of confusing them with useless details. It doesn't matter that Solr uses Jetty internally. As for running Solr on WebSphere/Tomcat without a WAR...that's not going to happen. Unless you want to fork Solr and keep the WAR... - Bram
