[cvs] expresso commit by mtraum: removed references to application specific

[JCorporate Ltd]

Log Message:
-----------
removed references to application specific xxxLogging.xml file. Only expressoLogging.xml is supported.

Modified Files:
--------------
    expresso/expresso-web/expresso/doc/edg:
        deploy.xml
        logging.xml
        healthcheck.xml

Revision Data
-------------
Index: logging.xml
===================================================================
RCS file: /home/javacorp/.cvs/expresso/expresso/expresso-web/expresso/doc/edg/logging.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -Lexpresso-web/expresso/doc/edg/logging.xml -Lexpresso-web/expresso/doc/edg/logging.xml -u -r1.6 -r1.7
--- expresso-web/expresso/doc/edg/logging.xml
+++ expresso-web/expresso/doc/edg/logging.xml
@@ -113,12 +113,9 @@
 		<para>
 The LogManager class is Expresso's interface to the Apache Log4j framework,
 and is used to set up logging for all applications in a particular environment.
-When ConfigManager first calls LogManager during system startup, all files
-with names of the form "*Logging.xml" in the configuration directory are
-read, and logging channels are then available for each of the channels
-defined in these files. This allows each application to have it's own seperate
-logging configuration file, e.g. expressoLogging.xml for Expresso's own
-internal classes, eForumLogging.xml for eForum, and so forth.
+When ConfigManager first calls LogManager during system startup, "expressoLogging.xml"
+in the configuration directory is read, and logging channels are then available for 
+each of the channels defined in these files.
 		</para>
 		<para>
 The primary means for monitoring the intranet system is via a log. All
@@ -584,20 +581,15 @@
 			</listitem>
 			<listitem>
 				<para>
-<emphasis role='bold'>Create your own logging xml file</emphasis>: After
-the design decisions are made, you'll want to create your own logging xml
-file and put it in your configuration directory. Expresso's LogManager
-will automatically load all xml files in the configuration directory and
-merge the categories into the existing expressoLogging.xml category tree.
-Please note: Do not define your own &lt;root&gt; node - Expresso already
-defines its own root node, and your own root will conflict with the rest
-of the system.
+<emphasis role='bold'>Add your logging info to expresoLogging.xml</emphasis>: After
+the design decisions are made, you'll want to add the logging settings
+fto expresoLogging.xml in your configuration directory.
 				</para>
 			</listitem>
 			<listitem>
 				<para>
 <emphasis role='bold'>Add logging code as detailed above</emphasis>: After
-your own logging.xml file is created, you can then add logging code to
+your logging info is added to expresoLogging.xml, you can then add logging code to
 your own application.
 				</para>
 			</listitem>
Index: healthcheck.xml
===================================================================
RCS file: /home/javacorp/.cvs/expresso/expresso/expresso-web/expresso/doc/edg/healthcheck.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -Lexpresso-web/expresso/doc/edg/healthcheck.xml -Lexpresso-web/expresso/doc/edg/healthcheck.xml -u -r1.5 -r1.6
--- expresso-web/expresso/doc/edg/healthcheck.xml
+++ expresso-web/expresso/doc/edg/healthcheck.xml
@@ -250,8 +250,8 @@
 Log4j, which is the integrated logging mechanism built into Expresso, is
 a very capable package, and it's performance impact is very small compared
 to many logging methods. Still, the fastest logging is no logging at all,
-and careful adjustment of the expressoLogging.xml file, and the corresponding
-file for your custom application can result in a large performance benefit.
+and careful adjustment of the expressoLogging.xml file can result in a large 
+performance benefit.
 					</para>
 					<para>
 The first logging issue to look for is of course to select the appropriate
Index: deploy.xml
===================================================================
RCS file: /home/javacorp/.cvs/expresso/expresso/expresso-web/expresso/doc/edg/deploy.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -Lexpresso-web/expresso/doc/edg/deploy.xml -Lexpresso-web/expresso/doc/edg/deploy.xml -u -r1.14 -r1.15
--- expresso-web/expresso/doc/edg/deploy.xml
+++ expresso-web/expresso/doc/edg/deploy.xml
@@ -94,14 +94,15 @@
 					</listitem>
 					<listitem>
 						<para>
-<emphasis role='bold'>config/XXXLogging.xml</emphasis>: The new application
+<emphasis role='bold'>WEB-INF/config/XXXLogging.xml</emphasis>: The new application
 will also probably install a file in the "config" sub-directory to define
 it's logging setup for Expresso to use with Log4j (the logging sub-system
 integrated with Expresso). If "config" is not the configuration directory
 your installation is using (which is should *not* be for a production system),
 you should move or copy this file to the configuration directory (this
 is the same directory in which is found expressoLogging.xml, default.properties,
-and other setup files).
+and other setup files). This file will not be read by expresso, but must be merged
+with expressoLogging.xml in order to enable the application specific logging.
 						</para>
 					</listitem>
 				</itemizedlist>