On 10/7/2016 10:33 AM, Renee Sun wrote: > 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?
For right now, Solr is still a webapp. It is not packaged as a .war file, but the information that would have been extracted from a .war file is still there, in exactly the same layout. It is already exploded, and the included Jetty accesses it as a webapp directly. You should be able to add the exploded webapp to another container like you would a .war file ... although you are on your own to make it work if you choose this path. https://wiki.apache.org/solr/WhyNoWar Eventually, no idea when, Solr will become a true standalone application, not a webapp. It is likely that this will be initially accomplished by embedding Jetty directly into the code, so internally Solr will remain much the same ... but after we pass that point, Solr will be free to evolve considerably. Thanks, Shawn
