Suggestion :
Don't call this embedded Jetty to avoid confusion with the actual embedded
jetty.

Otis
Solr & ElasticSearch Support
http://sematext.com/
On Apr 23, 2013 4:56 PM, "Furkan KAMACI" <furkankam...@gmail.com> wrote:

> Thanks for the answers. I will go with embedded Jetty for my SolrCloud. If
> I face with something important I would want to share my experiences with
> you.
>
> 2013/4/23 Shawn Heisey <s...@elyograg.org>
>
> > On 4/23/2013 2:25 PM, Furkan KAMACI wrote:
> >
> >> Is there any documentation that explains using Jetty as embedded or
> not? I
> >> use Solr deployed at Tomcat but after you message I will consider about
> >> Jetty. If we think about other issues i.e. when I want to update my Solr
> >> jars/wars etc.(this is just an foo example) does any pros and cons
> Tomcat
> >> or Jetty has?
> >>
> >
> > The Jetty in the example is only 'embedded' in the sense that you don't
> > have to install it separately.  It is not special -- the Jetty components
> > are not changed at all, a subset of them is just included in the Solr
> > download with a tuned configuration file.
> >
> > If you go to www.eclipse.org/jetty and download the latest stable-8
> > version, you'll see some familiar things - start.jar, an etc directory, a
> > lib directory, and a contexts directory.  They have more in them than the
> > example does -- extra functionality Solr doesn't need.  If you want to
> > start the downloaded version, you can use 'java -jar start.jar' just like
> > you do with Solr.
> >
> > Thanks,
> > Shawn
> >
> >
>

Reply via email to