You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-commits@lucene.apache.org by eh...@apache.org on 2008/03/25 02:40:03 UTC
svn commit: r640667 - /lucene/solr/trunk/src/webapp/web/WEB-INF/web.xml
Author: ehatcher
Date: Mon Mar 24 18:40:00 2008
New Revision: 640667
URL: http://svn.apache.org/viewvc?rev=640667&view=rev
Log:
Enlighted by Hoss' question, clarify a bit more about nesting Solr within a larger web application
Modified:
lucene/solr/trunk/src/webapp/web/WEB-INF/web.xml
Modified: lucene/solr/trunk/src/webapp/web/WEB-INF/web.xml
URL: http://svn.apache.org/viewvc/lucene/solr/trunk/src/webapp/web/WEB-INF/web.xml?rev=640667&r1=640666&r2=640667&view=diff
==============================================================================
--- lucene/solr/trunk/src/webapp/web/WEB-INF/web.xml (original)
+++ lucene/solr/trunk/src/webapp/web/WEB-INF/web.xml Mon Mar 24 18:40:00 2008
@@ -40,6 +40,16 @@
You will need to put this prefix in front of the SolrDispatchFilter
url-pattern mapping too (/solr/*), and also on any paths for
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>
<param-name>path-prefix</param-name>
<param-value>/xxx</param-value>