So, it sounds like that either Solr is treated as a webapp, in which case it is installed with most of the webapps under Tomcat (legacy/operational reason). So, Solr docs just needs to explain how to deploy under Tomcat and the rest of document/tooling comes from Tomcat community.
Or, if Solr is treated not as a webapp but as a black box, it needs to support and explain all the operational requirements (deployment, extension, monitoring) that are currently waved away as a 'container issue'. Regards, Alex. P.s. I also agree that example directory layout is become very confusing and may need to be re-thought. Probably a discussion for a different thread, if somebody has a thought out suggestion. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Tue, Nov 12, 2013 at 8:32 PM, Gopal Patwa <gopalpa...@gmail.com> wrote: > My case is also similar to "Sujit Pal" but we have jboss6. > > > On Tue, Nov 12, 2013 at 9:47 AM, Sujit Pal <sujit....@comcast.net> wrote: > > > In our case, it is because all our other applications are deployed on > > Tomcat and ops is familiar with the deployment process. We also had > > customizations that needed to go in, so we inserted our custom JAR into > the > > solr.war's WEB-INF/lib directory, so to ops the process of deploying Solr > > was (almost, except for schema.xml or solrconfig.xml changes) identical > to > > any of the other apps. But I think if Solr becomes a server with clearly > > defined extension points (such as dropping your custom JARs into lib/ and > > custom configuration in conf/solrconfig.xml or similar like it already > is) > > then it will be treated as something other than a webapp and the > > expectation that it runs on Tomcat will not apply. > > > > Just my $0.02... > > > > Sujit > > > > > > > > On Tue, Nov 12, 2013 at 9:13 AM, Siegfried Goeschl <sgoes...@gmx.at> > > wrote: > > > > > Hi ALex, > > > > > > in my case > > > > > > * ignorance that Tomcat is not fully supported > > > * Tomcat configuration and operations know-how inhouse > > > * could migrate to Jetty but need approved change request to do so > > > > > > Cheers, > > > > > > Siegfried Goeschl > > > > > > On 12.11.13 04:54, Alexandre Rafalovitch wrote: > > > > > >> Hello, > > >> > > >> I keep seeing here and on Stack Overflow people trying to deploy Solr > to > > >> Tomcat. We don't usually ask why, just help when where we can. > > >> > > >> But the question happens often enough that I am curious. What is the > > >> actual > > >> business case. Is that because Tomcat is well known? Is it because > other > > >> apps are running under Tomcat and it is ops' requirement? Is it > because > > >> Tomcat gives something - to Solr - that Jetty does not? > > >> > > >> It might be useful to know. Especially, since Solr team is considering > > >> making the server part into a black box component. What use cases will > > >> that > > >> break? > > >> > > >> So, if somebody runs Solr under Tomcat (or needed to and gave up), > let's > > >> use this thread to collect this knowledge. > > >> > > >> Regards, > > >> Alex. > > >> Personal website: http://www.outerthoughts.com/ > > >> LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch > > >> - Time is the quality of nature that keeps events from happening all > at > > >> once. Lately, it doesn't seem to be working. (Anonymous - via GTD > > book) > > >> > > >> > > >
