Enlighted by Hoss' question, clarify a bit more about nesting Solr within a larger web application

git-svn-id: https://svn.apache.org/repos/asf/lucene/solr/trunk@640667 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Erik Hatcher 2008-03-25 01:40:00 +00:00
parent 01b7029218
commit f0f2b88680
1 changed files with 10 additions and 0 deletions

View File

@ -40,6 +40,16 @@
You will need to put this prefix in front of the SolrDispatchFilter You will need to put this prefix in front of the SolrDispatchFilter
url-pattern mapping too (/solr/*), and also on any paths for url-pattern mapping too (/solr/*), and also on any paths for
legacy Solr servlet mappings you may be using. legacy Solr servlet mappings you may be using.
For the admin JSP's to work properly in a path-prefixed configuration,
the admin folder containing the JSPs needs to be under the app context root
named to match the path-prefix. For example:
.war
xxx
admin
stats.jsp
-->
<!--
<init-param> <init-param>
<param-name>path-prefix</param-name> <param-name>path-prefix</param-name>
<param-value>/xxx</param-value> <param-value>/xxx</param-value>