Yeah I second Matt's recommendation. But that said if you _really_ want to couple additional code with Solr, you might want to consider the reverse direction -- deploying your customizations as a servlet within Solr's Jetty. That is more "supportable" from a Solr perspective, relatively speaking. Depending on how you hook in, you can get access to the Solr CoreContainer etc if you need that level of access. Not that EmbeddedSolrServer isn't "supported" (it's certainly not going away) but I wouldn't use ESS for anything but embedded use cases and/or tests. Using ESS in DropWizard means more dependency issues to contend with. I've had to deal with some of that pain once because I had ESS (and thus all of Solr) on the test classpath with DropWizard.
~ David On Monday, April 3, 2017 at 4:30:17 PM UTC-4, Matt Pearce wrote: > > > I've always run Solr standalone (or in a separate container), and built > Dropwizard applications that talk to Solr through SolrJ. I wouldn't > personally try to run Solr inside Dropwizard's Jetty - Dropwizard is more > of an application framework than a container for other services. > > On Monday, 3 April 2017 18:58:30 UTC+1, Anurag Laddha wrote: >> >> Any update? >> Is it possible to load solr (or any .war for that matter) in embedded >> jetty of dropwizard? If yes, can you please point me to some documentation? >> >> Thanks! >> >> On Sunday, April 2, 2017 at 5:15:17 PM UTC+5:30, Anurag Laddha wrote: >>> >>> I am new to dropwizard and Apache Solr. >>> We are using an old version of Solr which requires to be loaded in a >>> servlet container >>> Is it possible to load solr (or any .war for that matter) in embedded >>> jetty of dropwizard? >>> >>> Thanks! >>> >> -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
