[
https://issues.apache.org/jira/browse/WICKET-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509096
]
Gili commented on WICKET-711:
-----------------------------
Agreed, examples has dependency, not core. Would it be possible to remove this
dependency (lower the priority if needed)?
Gwyn, there are two reasons I would push for logback:
1) Superior logging format
2) Better performance
Here is a quote for #2: "Certain critical operations, for instance determining
whether a log statement should be logged or not, has been significantly
improved. This operation takes about 3 nanoseconds in logback versus 30
nanoseconds in log4j. Logback also creates loggers faster : 13 microseconds
instead versus 23 microseconds for log4j. More importantly, it fetches an
existing logger in 94 nanoseconds versus 2234 nanoseconds for log4j, a 23 fold
improvement. The improvement over JUL is also far from insignificant."
I wish I could find you some reference output so you see what I mean for #1...
Off the top of my head by default you get the current thread name when logging
and if the log line is too long logback automatically collapses package names
down to single characters (so long as they are unique) so the log is easier to
read while containing even more useful information.
PS: I love the user manual of SimpleLog :) Very witty!
> Remove log4j dependency
> -----------------------
>
> Key: WICKET-711
> URL: https://issues.apache.org/jira/browse/WICKET-711
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.0-beta1
> Reporter: Gili
>
> Please consider removing Wicket's dependency on log4j. This can be achieved
> quite easily by replacing slf-log4j*.jar by slf4j-simple*.jar. The
> application footprint will shrink and all those ClassLoader problems log4j is
> notorious for will go away: http://www.qos.ch/logging/classloader.jsp
> Finally, I recommend you consider migrating to logback, which is a native
> implementation of slf4j by the author of log4j: http://logback.qos.ch/
> It's logging performance and output format is above and beyond what log4j
> provides. Once you try it you'll fall in love with the output format. Just my
> 2 cents :)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
