[
https://issues.apache.org/jira/browse/JSPWIKI-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648005#action_12648005
]
Ceki Gulcu commented on JSPWIKI-376:
------------------------------------
Hello Harry, Janne,
The SLF4J FAQ discusses this issue. Quoting from the FAQ [1], SLF4J is
only a facade, meaning that it does not provide a complete logging
solution. Operations such as configuring appenders or setting logging
levels cannot be performed with SLF4J. Thus, at some point in time,
any non-trivial application will need to directly invoke the
underlying logging system. In other words, complete independence from
the API underlying logging system is not possible for a stand-alone
application. Nevertheless, SLF4J reduces the impact of this dependence
to near-painless levels.
Still quoting the FAQ [1], suppose that your CRM application uses
log4j for its logging. However, one of your important clients request
that logging be performed through JDK 1.4 logging. If your application
is riddled with thousands of direct log4j calls, migration to JDK 1.4
would be a long and error-prone process. Had you been invoking SLF4J
API instead of log4j, the migration could be completed in a matter of
minutes instead of hours.
SLF4J lets component developers to defer the choice of the logging
system to the end-user but eventually a choice needs to be made.
One more thing. I wrote the log4j MBeans code. It's one of the more
sophisticated pieces of code in log4j. However, from a
user-friendliness point of view it is not worth the electrons it's
written on. I am sure you can do much better in JSPWiki. But I am
digressing.
At present time, SLF4J is a reasonable choice as a logging API but
they are other valid choices. In the case of JSPWiki, I would not
waste too much time about worrying logging. The success of JSPWiki
does not hinge on it. I hope you don't mind my unsolicited advice.
[1] http://slf4j.org/faq.html#when
> Move from log4j to slf4j
> ------------------------
>
> Key: JSPWIKI-376
> URL: https://issues.apache.org/jira/browse/JSPWIKI-376
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Reporter: Janne Jalkanen
> Assignee: Harry Metske
> Priority: Minor
> Fix For: 3.0
>
>
> SLF4J allows far more flexible logging than log4j, and it would allow us to
> get rid of these dumb log4j compatibility problems that sometimes occur. It
> also plays better with other applications, gives the user more power to
> choose how to log his stuff, and is also pretty cool otherwise. The change
> would be relatively trivial, and would probably be largely invisible to the
> users (since we could continue shipping with necessary log4j jars).
> http://www.slf4j.org
> The license is MIT/X11, so that's fine.
> Opinions?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
