The branch, master has been updated via 8c91c8ff649bc3222753049d487b276a240ec182 (commit) from 0195ace88a9616bbd43c81d7eed6c1561d7e4ee1 (commit)
Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- http://git.qos.ch/gitweb/?p=slf4j.git;a=commit;h=8c91c8ff649bc3222753049d487b276a240ec182 http://github.com/ceki/slf4j/commit/8c91c8ff649bc3222753049d487b276a240ec182 commit 8c91c8ff649bc3222753049d487b276a240ec182 Author: Ceki Gulcu <c...@qos.ch> Date: Sat Oct 31 05:43:00 2009 +0100 - in index.html added links to the migrator tool and the page on brinding legacy apis - minor editing in legacy.html diff --git a/slf4j-site/src/site/pages/index.html b/slf4j-site/src/site/pages/index.html index 7332970..764e18f 100644 --- a/slf4j-site/src/site/pages/index.html +++ b/slf4j-site/src/site/pages/index.html @@ -36,6 +36,17 @@ the two-page <a href="manual.html">SLF4J user manual</a>. </p> + <p>In case you wish to migrate your Java source files to SLF4J, + consider our <a href="migrator.html">migrator tool</a> which can + migrate your project into SLF4J in minutes.</p> + + <p>In case an externally-maintained component you depend on uses a + logging API other than SLF4J, such as commons logging, log4j or + j.u.l, have a look at SLF4J's binary-support for <a + href="legacy.html">legacy APIs</a>. + </p> + + <script src="templates/footer.js" type="text/javascript"></script> </div> </body> diff --git a/slf4j-site/src/site/pages/legacy.html b/slf4j-site/src/site/pages/legacy.html index e729d82..598b494 100644 --- a/slf4j-site/src/site/pages/legacy.html +++ b/slf4j-site/src/site/pages/legacy.html @@ -186,7 +186,7 @@ log4j. The presence of <em>log4j-over-slf4j.jar</em> will in turn delegate all log4j API calls to their SLF4J equivalents. If both are present simultaneously, slf4j calls will be delegated to log4j, and - log4j calls redirected to SLF4j, resulting in an endless recursion. + log4j calls redirected to SLF4j, resulting in an endless loop. </p> <h3><a name="jul-to-slf4j" href="jul-to-slf4j">JUL to SLF4J</a></h3> @@ -202,16 +202,15 @@ log4j-over-slf4j, which re-implement JCL and respectively log4j, the jul-to-slf4j modules does not re-implement the java.util.logging package because packages under the java.* - namespace cannot be replaced. Instead, translates LogRecord into - their SLF4J equivalents. Please note that translating - java.util.logging events into SLF4J incurs the cost of - constructing <a + namespace cannot be replaced. Instead, translates <a href="http://java.sun.com/j2se/1.5.0/docs/api/java/util/logging/LogRecord.html?is-external=true">LogRecord</a> - instance regardless of whether the SLF4J logger is disabled for - the given level or nor. <b>Consequently, j.u.l. to SLF4J translation - can seriously impact on the cost of disabled logging statements - (60 fold increase) and a measurable impact on enabled log - statements (20% overall increase).</b> + object into its SLF4J equivalent on each logging event. Please + note this traslation process incurs the cost of constructing a + <code>LogRecord</code> instance regardless of whether the SLF4J + logger is disabled for the given level or nor. <b>Consequently, + j.u.l. to SLF4J translation can seriously impact on the cost of + disabled logging statements (60 fold increase) and a measurable + impact on enabled log statements (20% overall increase).</b> </p> <p>If application performance is a concern, then use of ----------------------------------------------------------------------- Summary of changes: slf4j-site/src/site/pages/index.html | 11 +++++++++++ slf4j-site/src/site/pages/legacy.html | 19 +++++++++---------- 2 files changed, 20 insertions(+), 10 deletions(-) hooks/post-receive -- SLF4J: Simple Logging Facade for Java _______________________________________________ dev mailing list dev@slf4j.org http://www.slf4j.org/mailman/listinfo/dev