Hi Matthew,

your problem sounds like you want to run something alongside Solr, that
probably uses Solr. Since current versions of Solr basically require you to
go over HTTP, you could deploy the thing you would like to run in the root
context in a separate application container that accesses Solr over HTTP.

Alternatively, if the path is the only issue, you could just put a reverse
proxy in front of your application server and re-map the path to you
context that sits beside Solr.

Making changes like the ones you are suggesting are difficult in current
versions of Solr, where everything is coupled tightly to Jetty, so I hope
my suggestions can inspire you to find the perfect solution for this
problem.

Best regards,
Chris

On Mon, Nov 7, 2016 at 6:14 PM, matthew grisius <matthew.gris...@comcast.net
> wrote:

> I previously asked this question and did not receive any suggestions.
> I also asked on Jetty-Users and one person suggested I ask again here so I
> thought it might be worth it to ask again.
>
> Solr is deployed to “/solr” and is then mapped to “/“, e.g.
> http://localhost:8983/ <http://localhost:8983/> gets mapped to
> http://localhost:8983/solr/# <http://localhost:8983/solr/#>.
> I want to put a different servlet at “/“ while preserving Solr
> functionality at “/solr”.
> The reason for this is that I previously deployed my app with Solr on
> tomcat/tomee via war file and now want to use a current Solr release using
> Solr/Jetty.
>
> I thought the way to accomplish that was to re-assign  the "root context",
> e.g. contextPath =“/“ but cannot find a way to do this with Solr/Jetty.
>
> My unsuccessful attempts included:
>
> - edit contexts/solr-jetty-context.xml (contextPath, add resourceBase,
> etc.)
> - unmap solr rewrite rule to pass thru . . .
> - edit other '/contexts/' . . .
> - edit etc/webdefault.xml . . .
> - bin/solr does not appear to affect "/"
> - org.apache.solr.util.SolrCLI does not appear to affect "/"
>
> Perhaps I’m not trying the right combination of things in the right order
> to solve the issue, but I’ve run out of simple ideas to try.
>
> Does anyone have any other suggestions?
> Thank you, any help would be appreciated!
>
> -matt.

Reply via email to