At this point you can. At this point you have a war file anyway, so... Eventually this will be unsupported, I expect that _eventually_ there'll be a change that makes this no longer possible.
So my question back to you is why you have to run Solr in a servlet container? Why not just use the start script? Would you insist on running MySQL in a servlet container? Best, Erick On Mon, May 18, 2015 at 7:07 AM, Steven White <swhite4...@gmail.com> wrote: > Thanks Shawn and Upayavira. > > What about the second part of my question? I guess I was not clear on it, > so let me try again. Lets say I want to use Solr in a container other that > Jetty, such as WebSphere or Tomcat. If the WAR will be deprecated, is it a > matter of copying other Solr files into that container or is this not > possible? > > Steve > > On Mon, May 18, 2015 at 9:28 AM, Shawn Heisey <apa...@elyograg.org> wrote: > >> On 5/18/2015 6:42 AM, Steven White wrote: >> > With regards to Solr 5.0+, can someone point me where I can find out more >> > on: >> > >> > 1) Why WAR support is deprecated and is being dropped from Solr? and >> > 2) How do I deploy Solr 5.1 in a servlet other than Jetty, such as >> > WebSphere? >> >> As of 5.1, and probably for several releases after that, there is still >> a .war file, in the server/webapps directory that you will find in the >> binary download. If you deploy the war and some logging jars in your >> container, just like you would for 4.x versions as of 4.3, it will work >> perfectly. >> >> The reason that our docs are saying that we are no longer supporting >> running Solr in a third party container, even though it is still >> possible, is very simple: Eventually it won't be possible, and we hope >> to make it happen in a future 5.x version. >> >> There has been discussion underway for quite some time about turning >> Solr into a completely standalone application, so there won't be a .war >> file. There are a number of reasons for this move, but most of them >> boil down to one particular reason: >> >> Currently Solr has zero control over the HTTP and network layers. Solr >> doesn't even know what port it is listening on, until it actually >> receives a request from the outside world, which is far too late to do >> anything useful. A whole series of limitations are rooted in these facts. >> >> I put a stub page into the wiki which I will be expanding into a larger >> discussion when I have a few moments: >> >> https://wiki.apache.org/solr/WhyNoWar >> >> Thanks, >> Shawn >> >>
