root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

SPR-4493 

+ added some clarifications
+ improved the document structure
This commit is contained in:
Costin Leau 2010-01-26 14:31:44 +00:00
parent ead5df4546
commit 1152d51c6f
1 changed files with 31 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

66
spring-framework-reference/src/aop.xml
View File

@ -3624,7 +3624,7 @@ http://www.springframework.org/schema/context
<section id="aop-aj-ltw-environment-tomcat"> <section id="aop-aj-ltw-environment-tomcat">
<title>Tomcat</title> <title>Tomcat</title>
<para><ulink url="http://tomcat.apache.org/">Apache Tomcat's</ulink> default class loader <para><ulink url="http://tomcat.apache.org/">Apache Tomcat</ulink>'s default class loader
does not support class transformation which is why Spring provides an enhanced implementation that does not support class transformation which is why Spring provides an enhanced implementation that
addresses this need. Named <classname>TomcatInstrumentableClassLoader</classname>, the loader works addresses this need. Named <classname>TomcatInstrumentableClassLoader</classname>, the loader works
on Tomcat 5.0 and above and can be registered individually for <emphasis>each</emphasis> web application on Tomcat 5.0 and above and can be registered individually for <emphasis>each</emphasis> web application
@ -3653,22 +3653,19 @@ http://www.springframework.org/schema/context
loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader"/&gt; loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader"/&gt;
&lt;/Context&gt;</programlisting> &lt;/Context&gt;</programlisting>
<para>Apache Tomcat 6.0.x (similar to 5.0.x/5.5.x) series <para>Apache Tomcat 6.0.x (similar to 5.0.x/5.5.x) series supports several context locations:</para>
supports several context locations: <!--same as before; I can't tell what the different context locations are. It seems like there are only two, not *several*. <itemizedlist>
TR: OK AS IS. See below.-->server configuration file <listitem>server configuration file - <emphasis>$CATALINA_HOME/conf/server.xml</emphasis> </listitem>
(<emphasis>$CATALINA_HOME/conf/server.xml</emphasis>), the <listitem>default context configuration - <emphasis>$CATALINA_HOME/conf/context.xml</emphasis> - that
default context configuration affects all deployed web applications</listitem>
(<emphasis>$CATALINA_HOME/conf/context.xml</emphasis>) that <listitem>per-web application configuration which can be deployed either on the server-side at
affects all deployed web applications and per-web application <emphasis>$CATALINA_HOME/conf/[enginename]/[hostname]/[webapp]-context.xml</emphasis> or embedded inside
configurations, <!--change to per-web application? TR: OK.-->deployed the web-app archive at <emphasis>META-INF/context.xml</emphasis></listitem>
on the server side </itemizedlist>
<emphasis>($CATALINA_HOME/conf/[enginename]/[hostname]/my-webapp-context.xml</emphasis>) <para>For efficiency, the embedded per-web-app configuration style <!--Which one is inside the web-app config style? Reword. TR: REVISED, PLS REVIEW. Same change as for 5.0/5.5-->is
or inside the web application
(<emphasis>your-webapp.war/META-INF/context.xml</emphasis>).
For efficiency, inside the web-app configuration style <!--Which one is inside the web-app config style? Reword. TR: REVISED, PLS REVIEW. Same change as for 5.0/5.5-->is
recommended because it will impact only applications that use recommended because it will impact only applications that use
the custom class loader. See the Tomcat 6.0.x <ulink the custom class loader and does not require any changes to the server configuration.
url="http://tomcat.apache.org/tomcat-6.0-doc/config/context.html">documentation</ulink> See the Tomcat 6.0.x <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/config/context.html">documentation</ulink>
for more details about available context locations.</para> for more details about available context locations.</para>
</listitem> </listitem>
</orderedlist> </orderedlist>
@ -3695,19 +3692,16 @@ TR: OK AS IS. See below.-->server configuration file
loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader"/&gt; loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader"/&gt;
&lt;/Context&gt;</programlisting> &lt;/Context&gt;</programlisting>
<para>Tomcat 5.0.x and 5.5.x series support several context <para>Tomcat 5.0.x and 5.5.x series supports several context locations:</para>
locations: <!--Revise following sentences so it's clear what the context locations are. As written, it's hard to distinguish how many --><!--locations there are.Seems like only two, not *several*. TR: OK AS IS. There are four locations mentioned.-->server <itemizedlist>
configuration file <listitem>server configuration file - <emphasis>$CATALINA_HOME/conf/server.xml</emphasis> </listitem>
(<emphasis>$CATALINA_HOME/conf/server.xml</emphasis>), the <listitem>default context configuration - <emphasis>$CATALINA_HOME/conf/context.xml</emphasis> - that
default context configuration affects all deployed web applications</listitem>
(<emphasis>$CATALINA_HOME/conf/context.xml</emphasis>) that <listitem>per-web application configuration which can be deployed either on the server-side at
affects all deployed web applications and per-web application <emphasis>$CATALINA_HOME/conf/[enginename]/[hostname]/[webapp]-context.xml</emphasis> or embedded inside
configurations, <!--CHanged per-webapp to per-web application. If that's not right, what does it mean?-->deployed the web-app archive at <emphasis>META-INF/context.xml</emphasis></listitem>
on the server side </itemizedlist>
<emphasis>($CATALINA_HOME/conf/[enginename]/[hostname]/my-webapp-context.xml</emphasis>) <para>For efficiency, the embedded web-app configuration style<!--Which of the preceding is *inside the web-app config style*? Two paths contain webapp.
or inside the web application
(<emphasis>your-webapp.war/META-INF/context.xml</emphasis>).
For efficiency, inside the web-app configuration style<!--Which of the preceding is *inside the web-app config style*? Two paths contain webapp.
TR: REVISED, PLS REVIEW. Chnaged the last one to *inside*--> is recommended TR: REVISED, PLS REVIEW. Chnaged the last one to *inside*--> is recommended
recommended because it will impact only applications that use the class loader. See the Tomcat 5.x <ulink recommended because it will impact only applications that use the class loader. See the Tomcat 5.x <ulink
url="http://tomcat.apache.org/tomcat-5.5-doc/config/context.html">documentation</ulink> url="http://tomcat.apache.org/tomcat-5.5-doc/config/context.html">documentation</ulink>
@ -3716,20 +3710,22 @@ TR: REVISED, PLS REVIEW. Chnaged the last one to *inside*--> is recommended
<para>Tomcat versions prior to 5.5.20 contained a bug in the <para>Tomcat versions prior to 5.5.20 contained a bug in the
XML configuration parsing that prevented usage of the XML configuration parsing that prevented usage of the
<literal>Loader</literal> tag inside <literal>Loader</literal> tag inside
<emphasis>server.xml</emphasis>, regardless of whether a class <emphasis>server.xml</emphasis> configuration, regardless of whether a class
loader is specified or whether it is the official or a custom loader is specified or whether it is the official or a custom
one. See Tomcat's bugzilla for <ulink one. See Tomcat's bugzilla for <ulink
url="http://issues.apache.org/bugzilla/show_bug.cgi?id=39704">more url="http://issues.apache.org/bugzilla/show_bug.cgi?id=39704">more
details</ulink>.<!--Will reader know what Tomcat's bugzilla is and where to find it? TR: OK AS IS. They just need to click on the hyerlink.--></para> details</ulink>.</para><!--Will reader know what Tomcat's bugzilla is and where to find it? TR: OK AS IS. They just need to click on the hyerlink.-->
<para>In Tomcat 5.5.20 or later, you should set <para>In Tomcat 5.5.x, versions 5.5.20 or later, you should set
<emphasis>useSystemClassLoaderAsParent</emphasis> to <emphasis>useSystemClassLoaderAsParent</emphasis> to
<literal>false</literal> to fix this problem: <programlisting <literal>false</literal> to fix this problem:
</para>
<programlisting
language="xml">&lt;Context path="/myWebApp" docBase="/my/webApp/location"&gt; language="xml">&lt;Context path="/myWebApp" docBase="/my/webApp/location"&gt;
&lt;Loader &lt;Loader
loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader" loaderClass="org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader"
useSystemClassLoaderAsParent="false"/&gt; <emphasis role="bold">useSystemClassLoaderAsParent="false"</emphasis>/&gt;
&lt;/Context&gt;</programlisting></para> &lt;/Context&gt;</programlisting><para>This setting is not needed if using Tomcat 6 or higher.</para>
</listitem> </listitem>
</orderedlist> </orderedlist>
</itemizedlist> </itemizedlist>