I won't speak for the committers, but I'm guessing you won't find a lot of support for the idea of continuing to provide a WAR file with the standard SOLR releases...
I feel for you and your situation however - I've had to wrestle with a number of situations where a somewhat monolithic architecture was disturbed by newer ways of doing things... That leaves 2 options... A self-maintained build of the latest SOLR into a WAR file (challenging in it's own way) or the very least amount of code necessary to allow your Tomcat-based tools to talk to a 6.x Solr server running in Jetty... I imagine something better than re-writing all your code can be done, although I also don't think you can get away with no new code either... At a high level, some kind of API/message bus/interface comes to mind, but I don't know enough about your situation to be able to guess what might be a good approach. If you're interested in a discussion about how to approach the change, I'd be happy to offer ideas, but I'd need to know how your other tools currently talk to Solr... Of course, you may not want to even have that discussion if the task is just to big... On Fri, Oct 7, 2016 at 9:33 AM, Renee Sun <renee_...@mcafee.com> wrote: > Thanks ... but that is an extremely simplified situation. > > We are not just looking for Solr as a new tool to start using it. > > In our production, we have cloud based big data indexing using Solr for > many > years. We have developed lots business related logic/component deployed as > webapps working seamlessly with solr. > > I will give you a simple example, we purchased multi-lingual processors > (and > many other 3rd parties) which we integrated with solr by carefully deploy > the libraries (e.g.) in the tomcat container so they work together. This > basically means we have to rewrite all those components to make it work > with > solr 5 or 6. > > In my opinion, for those solr users like our company, it will really be > beneficial if Solr could keep supporting deploying a war and maintain > parallel support with its new standalone release, although this might be > too > much work? > > Thanks > Renee > > > > -- > View this message in context: http://lucene.472066.n3. > nabble.com/solr-5-leaving-tomcat-will-I-be-the-only-one- > fearing-about-this-tp4300065p4300202.html > Sent from the Solr - User mailing list archive at Nabble.com. >
