Update of /cvsroot/opensymphony/website/web/guidelines
In directory sc8-pr-cvs1:/tmp/cvs-serv8580/web/guidelines
Modified Files:
logging.jsp
Log Message:
Fixed bad link to log4j docs.
Index: logging.jsp
===================================================================
RCS file: /cvsroot/opensymphony/website/web/guidelines/logging.jsp,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- logging.jsp 29 Jul 2003 04:09:17 -0000 1.2
+++ logging.jsp 2 Sep 2003 08:37:24 -0000 1.3
@@ -1,96 +1,96 @@
-<html>
-<head>
- <title>Logging</title>
-</head>
-<body>
-
-<p>
-All OpenSymphony modules use the <a href="http://jakarta.apache.org/commons/logging.html">Jakarta Commons Logging</a> package.
-</p>
-
-<p>
-All usage of <code>System.out</code>, <code>System.err</code>, and <code>exception.printStackTrace()</code> are highly discouraged.<br>
-Use an appropriate Logger methods instead.
-</p>
-
-<p>
-Here's a 5 minute logging primer. For a real world usage example, see any of the current OpenSymphony modules.
-</p>
-
-<h4>Commons Logging / OpenSymphony Logging Primer</h4>
-
-<p>To initialise the logger, each class should have a static variable "log"
-created like so :</p>
-
-<blockquote><code>
-static Log log = LogFactory.getInstance(ThisClass.class);
-</code></blockquote>
-
-<p>
-The LogFactory will automatically pick up its configuration and implementation
-from the environment using a set of lookup rules, as outlined <a href="http://jakarta.apache.org/commons/logging/userguide.html#Configuring%20the%20Logger%20Implementation">here</a>
-</p>
-
-<p>
-To actually log statements, you then just need to do any of the following
-(in order of priority, lowest to highest):
-</p>
-
-<blockquote><code>
- log.info("A log statement");<br>
- log.debug("A log statement");<br>
- log.warn("A log statement");<br>
- log.error("A log statement");<br>
-</code></blockquote>
-
-<p>
-That's it.
-</p>
-
-<p>Usually, commons-logging is used as a wrapper around Log4j, which has its own configuration mechanism.
-<p>
-An example log4j configuration file (this will log statements of debug or higher priority to
-System.out) :
-</p>
-
-<blockquote><code><pre>
-# An example log4j configuration file that outputs to System.out.
-# The output info consists of relative time, priority, thread name,
-# category name, nested diagnostic context, the and the message in
-# that order.
-
-# For the general syntax of propperty based caonfiguration files see
-# the documenation of org.log4j.PropertyConfigurator.
-
-# The root category uses the appender called A1. Since no priority is
-# specified, the root category assumes the default priority for root
-# which is DEBUG in log4j. The root category is the only category that
-# has a default priority. All other categories do not have a default
-# priority. in which case the priority is inherited from the
-# hierarchy.
-
-log4j.rootCategory=, A1
-
-# A1 is set to be a FileAppender which outputs to System.out.
-log4j.appender.A1=org.log4j.FileAppender
-log4j.appender.A1.File=System.out
-
-# A1 uses PatternLayout.
-log4j.appender.A1.layout=org.log4j.PatternLayout
-
-# The conversion pattern uses format specifiers. You might want to
-# change the pattern an watch the output layout change.
-log4j.appender.A1.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
-</pre></code></blockquote>
-
-<p>
-You can do very versatile things by just changing the properties file (such
-as logging to a file, rolling file, syslog or NT event log, changing the
-output of the log, the priority levels etc).
-</p>
-
-<p>
-For more information see <a href="http://jakarta.apache.org/log4j/doc/documentation.html">the log4j documentation</a>.
-</p>
-</body>
-</html>
+<html>
+<head>
+ <title>Logging</title>
+</head>
+<body>
+
+<p>
+All OpenSymphony modules use the <a href="http://jakarta.apache.org/commons/logging.html">Jakarta Commons Logging</a> package.
+</p>
+
+<p>
+All usage of <code>System.out</code>, <code>System.err</code>, and <code>exception.printStackTrace()</code> are highly discouraged.<br>
+Use an appropriate Logger methods instead.
+</p>
+
+<p>
+Here's a 5 minute logging primer. For a real world usage example, see any of the current OpenSymphony modules.
+</p>
+
+<h4>Commons Logging / OpenSymphony Logging Primer</h4>
+
+<p>To initialise the logger, each class should have a static variable "log"
+created like so :</p>
+
+<blockquote><code>
+static Log log = LogFactory.getInstance(ThisClass.class);
+</code></blockquote>
+
+<p>
+The LogFactory will automatically pick up its configuration and implementation
+from the environment using a set of lookup rules, as outlined <a href="http://jakarta.apache.org/commons/logging/userguide.html#Configuring%20the%20Logger%20Implementation">here</a>
+</p>
+
+<p>
+To actually log statements, you then just need to do any of the following
+(in order of priority, lowest to highest):
+</p>
+
+<blockquote><code>
+ log.info("A log statement");<br>
+ log.debug("A log statement");<br>
+ log.warn("A log statement");<br>
+ log.error("A log statement");<br>
+</code></blockquote>
+
+<p>
+That's it.
+</p>
+
+<p>Usually, commons-logging is used as a wrapper around Log4j, which has its own configuration mechanism.
+<p>
+An example log4j configuration file (this will log statements of debug or higher priority to
+System.out) :
+</p>
+
+<blockquote><code><pre>
+# An example log4j configuration file that outputs to System.out.
+# The output info consists of relative time, priority, thread name,
+# category name, nested diagnostic context, the and the message in
+# that order.
+
+# For the general syntax of propperty based caonfiguration files see
+# the documenation of org.log4j.PropertyConfigurator.
+
+# The root category uses the appender called A1. Since no priority is
+# specified, the root category assumes the default priority for root
+# which is DEBUG in log4j. The root category is the only category that
+# has a default priority. All other categories do not have a default
+# priority. in which case the priority is inherited from the
+# hierarchy.
+
+log4j.rootCategory=, A1
+
+# A1 is set to be a FileAppender which outputs to System.out.
+log4j.appender.A1=org.log4j.FileAppender
+log4j.appender.A1.File=System.out
+
+# A1 uses PatternLayout.
+log4j.appender.A1.layout=org.log4j.PatternLayout
+
+# The conversion pattern uses format specifiers. You might want to
+# change the pattern an watch the output layout change.
+log4j.appender.A1.layout.ConversionPattern=%-4r %-5p [%t] %37c %3x - %m%n
+</pre></code></blockquote>
+
+<p>
+You can do very versatile things by just changing the properties file (such
+as logging to a file, rolling file, syslog or NT event log, changing the
+output of the log, the priority levels etc).
+</p>
+
+<p>
+For more information see <a href="http://jakarta.apache.org/log4j/docs/documentation.html">the log4j documentation</a>.
+</p>
+</body>
+</html>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.