Author: rjung
Date: Mon Dec 21 15:02:07 2009
New Revision: 892843
URL: http://svn.apache.org/viewvc?rev=892843&view=rev
Log:
Fix some comment typos.
Modified:
tomcat/trunk/java/org/apache/catalina/core/StandardContext.java
tomcat/trunk/java/org/apache/catalina/loader/WebappClassLoader.java
tomcat/trunk/webapps/docs/config/context.xml
Modified: tomcat/trunk/java/org/apache/catalina/core/StandardContext.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/core/StandardContext.java?rev=892843&r1=892842&r2=892843&view=diff
==============================================================================
--- tomcat/trunk/java/org/apache/catalina/core/StandardContext.java (original)
+++ tomcat/trunk/java/org/apache/catalina/core/StandardContext.java Mon Dec 21
15:02:07 2009
@@ -748,7 +748,7 @@
private boolean clearReferencesStatic = false;
/**
- * Should Tomcat attempt to termiate threads that have been started by the
+ * Should Tomcat attempt to terminate threads that have been started by the
* web application? Stopping threads is performed via the deprecated (for
* good reason) <code>Thread.stop()</code> method and is likely to result
in
* instability. As such, enabling this should be viewed as an option of
last
Modified: tomcat/trunk/java/org/apache/catalina/loader/WebappClassLoader.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/loader/WebappClassLoader.java?rev=892843&r1=892842&r2=892843&view=diff
==============================================================================
--- tomcat/trunk/java/org/apache/catalina/loader/WebappClassLoader.java
(original)
+++ tomcat/trunk/java/org/apache/catalina/loader/WebappClassLoader.java Mon Dec
21 15:02:07 2009
@@ -415,7 +415,7 @@
/**
* Should Tomcat attempt to null out any static or final fields from loaded
* classes when a web application is stopped as a work around for apparent
- * garbage collection bugs and application coding errors. There have been
+ * garbage collection bugs and application coding errors? There have been
* some issues reported with log4j when this option is true. Applications
* without memory leaks using recent JVMs should operate correctly with
this
* option set to <code>false</code>. If not specified, the default value of
@@ -424,9 +424,9 @@
private boolean clearReferencesStatic = false;
/**
- * Should Tomcat attempt to termiate threads that have been started by the
+ * Should Tomcat attempt to terminate threads that have been started by the
* web application? Stopping threads is performed via the deprecated (for
- * goo reason) <code>Thread.stop()</code> method and is likely to result in
+ * good reason) <code>Thread.stop()</code> method and is likely to result
in
* instability. As such, enabling this should be viewed as an option of
last
* resort in a development environment and is not recommended in a
* production environment. If not specified, the default value of
@@ -2007,9 +2007,9 @@
}
// This method is deprecated and for good reason. This is
- // very risky code but is only only option at this point
+ // very risky code but is the only option at this point.
// A *very* good reason for apps to do this clean-up
- // themselves
+ // themselves.
thread.stop();
}
}
Modified: tomcat/trunk/webapps/docs/config/context.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/context.xml?rev=892843&r1=892842&r2=892843&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/context.xml (original)
+++ tomcat/trunk/webapps/docs/config/context.xml Mon Dec 21 15:02:07 2009
@@ -340,12 +340,12 @@
</attribute>
<attribute name="clearReferencesStopThreads" required = "false">
- <p>If <code>true</code>, Tomcat attempts to termiate threads that have
- been started by the web application? Stopping threads is performed via
+ <p>If <code>true</code>, Tomcat attempts to terminate threads that have
+ been started by the web application. Stopping threads is performed via
the deprecated (for good reason) <code>Thread.stop()</code> method and
is likely to result in instability. As such, enabling this should be
viewed as an option of last resort in a development environment and is
- not recommended in a production environment.If not specified, the
+ not recommended in a production environment. If not specified, the
default value of <code>false</code> will be used.</p>
</attribute>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
