[jboss-cvs] JBossAS SVN: r100235 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: laubai
Date: 2010-02-02 00:24:37 -0500 (Tue, 02 Feb 2010)
New Revision: 100235

Modified:
   projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml
Log:
Added the fix for JBPAPP-3590.

Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml	2010-02-02 05:01:18 UTC (rev 100234)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Performance_Tuning.xml	2010-02-02 05:24:37 UTC (rev 100235)
@@ -223,14 +223,14 @@
 		<itemizedlist>
 			<listitem>
 				<para>
-					<property>jboss.vfs.forceCopy</property> - has the options true and false, with the default being false.
+					<property>jboss.vfs.forceCopy</property>
 				</para>
 				<para>
-					This defines how nested jars should be handled. If forceCopy equals true, we create a temporary copy of the nested jar, and re-wire VFS accordingly. If forceCopy equals false, we handle nested jars in-memory, which doesn't create temporary copy, but is more memory consuming. Currently JBoss Enterprise Application Platform forces temporary copy by default.
+					This defines how nested jars should be handled. If forceCopy is true (the default), we create a temporary copy of the nested jar, and re-wire VFS accordingly. If forceCopy is false, we handle nested jars in-memory, which doesn't create temporary copy, but is more memory consuming.
 				</para>
-				<para>
+				<!--<para>
 					If the <property>useCopyJarHandler</property> property is used as part of URI query, you can configure force-copy at runtime, per URI root (if it doesn't already exist).
-				</para>
+				</para>-->
 			</listitem>
 			<listitem>
 				<para>