From f0f2b88680762cffda820692f292ecc95fc2f4c1 Mon Sep 17 00:00:00 2001
From: Erik Hatcher <ehatcher@apache.org>
Date: Tue, 25 Mar 2008 01:40:00 +0000
Subject: [PATCH] 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
---
 src/webapp/web/WEB-INF/web.xml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/webapp/web/WEB-INF/web.xml b/src/webapp/web/WEB-INF/web.xml
index 3b1859e150a..4ddb9f6f292 100644
--- a/src/webapp/web/WEB-INF/web.xml
+++ b/src/webapp/web/WEB-INF/web.xml
@@ -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>