diff --git a/spring-framework-reference/src/aop.xml b/spring-framework-reference/src/aop.xml index 77ed9edec7d..4f6f07b0aee 100644 --- a/spring-framework-reference/src/aop.xml +++ b/spring-framework-reference/src/aop.xml @@ -3624,7 +3624,7 @@ http://www.springframework.org/schema/context
Tomcat - Apache Tomcat's default class loader + Apache Tomcat's default class loader does not support class transformation which is why Spring provides an enhanced implementation that addresses this need. Named TomcatInstrumentableClassLoader, the loader works on Tomcat 5.0 and above and can be registered individually for each web application @@ -3653,22 +3653,19 @@ http://www.springframework.org/schema/context loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader"/> </Context> - Apache Tomcat 6.0.x (similar to 5.0.x/5.5.x) series - supports several context locations: server configuration file - ($CATALINA_HOME/conf/server.xml), the - default context configuration - ($CATALINA_HOME/conf/context.xml) that - affects all deployed web applications and per-web application - configurations, deployed - on the server side - ($CATALINA_HOME/conf/[enginename]/[hostname]/my-webapp-context.xml) - or inside the web application - (your-webapp.war/META-INF/context.xml). - For efficiency, inside the web-app configuration style is + Apache Tomcat 6.0.x (similar to 5.0.x/5.5.x) series supports several context locations: + + server configuration file - $CATALINA_HOME/conf/server.xml + default context configuration - $CATALINA_HOME/conf/context.xml - that + affects all deployed web applications + per-web application configuration which can be deployed either on the server-side at + $CATALINA_HOME/conf/[enginename]/[hostname]/[webapp]-context.xml or embedded inside + the web-app archive at META-INF/context.xml + + For efficiency, the embedded per-web-app configuration style is recommended because it will impact only applications that use - the custom class loader. See the Tomcat 6.0.x documentation + the custom class loader and does not require any changes to the server configuration. + See the Tomcat 6.0.x documentation for more details about available context locations. @@ -3695,19 +3692,16 @@ TR: OK AS IS. See below.-->server configuration file loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader"/> </Context> - Tomcat 5.0.x and 5.5.x series support several context - locations: server - configuration file - ($CATALINA_HOME/conf/server.xml), the - default context configuration - ($CATALINA_HOME/conf/context.xml) that - affects all deployed web applications and per-web application - configurations, deployed - on the server side - ($CATALINA_HOME/conf/[enginename]/[hostname]/my-webapp-context.xml) - or inside the web application - (your-webapp.war/META-INF/context.xml). - For efficiency, inside the web-app configuration style is recommended recommended because it will impact only applications that use the class loader. See the Tomcat 5.x documentation @@ -3716,20 +3710,22 @@ TR: REVISED, PLS REVIEW. Chnaged the last one to *inside*--> is recommended Tomcat versions prior to 5.5.20 contained a bug in the XML configuration parsing that prevented usage of the Loader tag inside - server.xml, regardless of whether a class + server.xml configuration, regardless of whether a class loader is specified or whether it is the official or a custom one. See Tomcat's bugzilla for more - details. + details. - In Tomcat 5.5.20 or later, you should set + In Tomcat 5.5.x, versions 5.5.20 or later, you should set useSystemClassLoaderAsParent to - false to fix this problem: false to fix this problem: + + <Context path="/myWebApp" docBase="/my/webApp/location"> <Loader loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader" - useSystemClassLoaderAsParent="false"/> -</Context> + useSystemClassLoaderAsParent="false"/> +</Context>This setting is not needed if using Tomcat 6 or higher.