[jboss-cvs] JBossAS SVN: r77757 - in projects/docs/enterprise: 4.3.2.1/Seam/Seam_Reference_Guide and 1 other directories.

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

Author: irooskov at redhat.com
Date: 2008-09-01 20:05:40 -0400 (Mon, 01 Sep 2008)
New Revision: 77757

Modified:
   projects/docs/enterprise/4.2.5/Getting_Started/en-US/The_JBoss_Server___A_Quick_Tour.xml
   projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/Makefile
   projects/docs/enterprise/4.3.3/Getting_Started/en-US/The_JBoss_Server___A_Quick_Tour.xml
Log:
updated the Getting Started Guide with JBPAPP-845 fix for both 4.2.5 and 4.3.3


Modified: projects/docs/enterprise/4.2.5/Getting_Started/en-US/The_JBoss_Server___A_Quick_Tour.xml
===================================================================
--- projects/docs/enterprise/4.2.5/Getting_Started/en-US/The_JBoss_Server___A_Quick_Tour.xml	2008-09-01 15:56:13 UTC (rev 77756)
+++ projects/docs/enterprise/4.2.5/Getting_Started/en-US/The_JBoss_Server___A_Quick_Tour.xml	2008-09-02 00:05:40 UTC (rev 77757)
@@ -137,6 +137,11 @@
 			<para>
 				The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to the name. You will notice that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
 			</para>
+			<warning>
+				<para>
+					If you edit the <filename>jboss-log4j.xml</filename> file, be aware that the log4j configuration will be reloaded as if the server was restarted. Before editing the file, be aware that if the file appender is not configured to append to an existing log file, then the process will delete the current log and create a new file in its place.
+				</para>
+			</warning>
 		</section>
 		
 		<section id="Basic_Configuration_Issues-Security_Service">

Modified: projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/Makefile
===================================================================
--- projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/Makefile	2008-09-01 15:56:13 UTC (rev 77756)
+++ projects/docs/enterprise/4.3.2.1/Seam/Seam_Reference_Guide/Makefile	2008-09-02 00:05:40 UTC (rev 77757)
@@ -4,7 +4,7 @@
 
 XML_LANG	= en-US
 DOCNAME		= Seam_Reference_Guide
-PRODUCT		= Seam_Framework
+PRODUCT		= JBoss_Enterprise_Application_Platform
 BRAND		= JBoss
 
 TRANSLATIONS    = $(XML_LANG)

Modified: projects/docs/enterprise/4.3.3/Getting_Started/en-US/The_JBoss_Server___A_Quick_Tour.xml
===================================================================
--- projects/docs/enterprise/4.3.3/Getting_Started/en-US/The_JBoss_Server___A_Quick_Tour.xml	2008-09-01 15:56:13 UTC (rev 77756)
+++ projects/docs/enterprise/4.3.3/Getting_Started/en-US/The_JBoss_Server___A_Quick_Tour.xml	2008-09-02 00:05:40 UTC (rev 77757)
@@ -92,7 +92,7 @@
 		<section id="Basic_Configuration_Issues-Logging_Service">
 			<title>Logging Service</title>
 			<para>
-				In JBoss <literal>log4j</literal> is used for logging. If you are not familiar with the <literal>log4j</literal> package and would like to use it in your applications, you can read more about it at the Jakarta web site (<ulink url="http://jakarta.apache.org/log4j/"></ulink>).
+				In JBoss, <literal>log4j</literal> is used for logging. If you are not familiar with the <literal>log4j</literal> package and would like to use it in your applications, you can read more about it at the Jakarta web site (<ulink url="http://jakarta.apache.org/log4j/"></ulink>).
 			</para>
 			<para>
 				Logging is controlled from a central <filename>conf/log4j.xml</filename> file. This file defines a set of appenders specifying the log files, what categories of messages should go there, the message format and the level of filtering. By default, JBoss produces output to both the console and a log file (<filename>server.log</filename> in the <filename class="directory">log</filename> directory).
@@ -137,6 +137,11 @@
 			<para>
 				The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to the name. You will notice that the <filename class="directory">log</filename> directory also contains HTTP request logs which are produced by the web container.
 			</para>
+			<warning>
+				<para>
+					If you edit the <filename>jboss-log4j.xml</filename> file, be aware that the log4j configuration will be reloaded as if the server was restarted. Before editing the file, be aware that if the file appender is not configured to append to an existing log file, then the process will delete the current log and create a new file in its place.
+				</para>
+			</warning>
 		</section>
 		
 		<section id="Basic_Configuration_Issues-Security_Service">