Dear Christopher, my 5ct on that: We're using Solr for years like (and together with) all other Webapps on Tomcat (and since some month on Wildfly) in a "classic" (non-cloud) setup without any the need for special tweaks.
There is no official support for an webapp artifact since some Versions, but one just have to extract the web application tree from the release. I have no experience with embedded tomcat, but it should be also straight forward. Said that, I can't imagine the advantage of such an approach against the currently used, which just start the Web Application Server (Jetty, Tomcat or whatever) with the preinstalled Solr application. We even have used it in the other way round: We used an embedded Solr Server as a SolrMaster instead of a SolrClient within an Ingest application to avoid the "serialization/network overhead" of big Solr documents. This Application was also hosted together with others on our Tomcat plattform With greetings Guido >-----Original Message----- >From: Christopher Schultz [mailto:ch...@christopherschultz.net] >Sent: Sunday, October 14, 2018 3:41 AM >To: Tomcat Users List <users@tomcat.apache.org> >Subject: Tomcat embedded with Apache Solr > >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA256 > >All, > >I've posted a question to the Solr mailing list[1] about why Jetty is >being used instead of Tomcat, and it seems that it's just "always the >way it's been" for the most part. > >These seems to be some interest in moving from their existing model >(Jetty launches, then hosts Solr as a web application) to an embedded >model where a Solr-agent launches and then launches the app server >(e.g. tc) hosting itself. > >Is anyone familiar enough with Solr to whip-up a quick-and-dirty POC >for Tomcat-embedded-hosting-Solr? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
