[
https://issues.apache.org/jira/browse/SOLR-5333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett closed SOLR-5333.
-----------------------------------
Resolution: Won't Fix
Deploying Solr in containers is no longer supported as of Solr 5, and it's
unlikely any work will be done to resolve issues for 4.x or earlier.
https://wiki.apache.org/solr/WhyNoWar
> path prefix and admin interface
> -------------------------------
>
> Key: SOLR-5333
> URL: https://issues.apache.org/jira/browse/SOLR-5333
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.4
> Reporter: Mirko Perillo
> Priority: Minor
>
> Hi,
> I'm trying to include solr 4.4 in a larger webapplication.
> Comments in web.xml say that I can configure a path-prefix for solr stuff.
> To do this I read that I have to (i.e. under /search prefix) :
> 1. configure init-param of SolrRequestFilter with /search
> 2. change url-pattern of SolrRequestFilter with /search/*
> 3. move all admin interface in a subfolder search, so something like
> app.war/search/<admin_stuff>
> Doing this admin interface doesn't work, because admin.html contains some
> placeholder (${version},${contextPath},${adminPath}) that are replaced by
> LoadAdminUiServlet
> Reading source code I see that LoadAdminUiServlet this replacements is inside
> a if block
> InputStream in = getServletContext().getResourceAsStream("/admin.html");
> if(in != null && cores != null) {
> but in variable is null because admin.html has been moved in search subfolder.
> Have I misunderstood something ?
> thanks
> Mirko
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
