Hi
Does anybody know if it is it possible to use Logback on JDK1.4? I get an
UnsupportedClassVersionError when trying to instantiate a Logback logger
through SLF4J.
I've had a look at pom.xml and see that the jdkLevel is set to 1.5. So the
exception makes sense - I'm trying to run 1.5 code against a 1.4 jdk... That
said I find it strange the Logback only supports jdk1.5 and higher. Anybody
running it against a 1.4 jdk? If so, how did you manage to do it?
Thanks.
To be complete:
The code that I'm using is very simple:
Logger log = LoggerFactory.getLogger(InitLog.class);
log.debug(">>> Logging Initialized");
The exception I'm getting:
java.lang.UnsupportedClassVersionError: org/slf4j/LoggerFactory (Unsupported
major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code))
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled
Code))
at
com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:446)
at
com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java(Compiled
Code))
at
com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:300)
at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
at za.ibm.slftest.servlet.InitLog.init(InitLog.java:15)
Regards
Fouche du Preez
Log4J employs the Apache License and wound up being the inspiration for the
entire Logging Project at the ASF, why was the LGPL chosen as the license to
employ for Logback?
--
View this message in context: http://www.nabble.com/Why-LGPL-instead-of-Apache-License--tf2884320.html#a8…
Sent from the Logback User mailing list archive at Nabble.com.
For my current project I would like to switch out all the logging which is
currently being done by log4j and here en there by commons-logging to one
framework. After some searching I discoverd SLF4J and Logback as the
successor to log4j. In your code I swapped out all the log4j and
commons-logging to the SLF4J api and I want to use Logback as my logger. I
converted our log4j.properties file with the configuration converter on the
website, so I assume that is correct.
In the tomcat directory I have the following logging libs (I want tomcat to
use SLF4J to)
commons/lib/commons-logging-1.1.jar
commons/lib/jcl104-over-slf4j-1.1.0-RC1.jar
commons/classes/logback.xml
In our webapplication (which is a packaged war and doesn't get unpacked!) I
have
WEB-INF/lib/slf4j-api-1.1.0-RC1.jar
WEB-INF/lib/logback-classic-0.7.jar
WEB-INF/lib/logback-core-0.7.jar
WEB-INF/classes/logback.xml
The contents of the logback.xml in the commons directory just contains a
simple ConsoleAppender and is configured to WARN level.
The file in the WEB-INF directory is configured as a file which should be
written to c:\logs\mylog.log, configured different levels for different
packages we use.
However logback isn't getting picked up, everything is being logged by the
java.util classes (as it appears thatone is being initialized by tomcat
instead of the logback logger).
I tried different configurations, all the logback/slf4j jars in the
commons/lib and one config file in commons/classes. Different jars in
commons/lib and WEB-INF/lib but until now everytime with the same result,
only logging to JUL and nothing to logback and my configured logfile.
Currently I'm at a loss on what to do and how to make it work. I need some
assistance with this.
Kind Regards,
Marten
--
View this message in context: http://www.nabble.com/Trouble-setting-up-logback-in-tomcat.-tf2858698.html#…
Sent from the Logback User mailing list archive at Nabble.com.
December 18th, 2006 - Release of version 0.7
Version 0.7 of logback has been released.
Logback now ships with a new module: log4j-bridge. This new module can be used to
intercept log4j calls and redirects them to logback components. More information
about this module can be found in the corresponding documentation page[1].
The documentation has been vastly updated. Two new chapters, namely Filters and MDC,
are available in the manual section[2].
Links:
[1] http://logback.qos.ch/bridge.html
[2] http://logback.qos.ch/manual/index.html
--
Sébastien Pennec
sebastien(a)qos.ch
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch/
Hello all,
In case you wish to reach us by IRC, Sebastien and I are often available at
irc.freenode.net#logback
Cheers,
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
Hi,
one major advantage(to me, i acknowledge ;-) ) of the java.util.logging
package over log4j and other logging libraries is its security.
it uses the underlying java security infrastructure by securing logs with
loggingpermission use.
have you any plan to use loggingpermission?
it can be used very easily to control any logging configuration change.
other use case can stands on loggingpermission to prevent some programers to
use loggers of some packages for example.
if you are interested to implemented this feature, i can help you to
understand java security internals if needed.
cheers,
Charles GAY
www.jguard.net
--
View this message in context: http://www.nabble.com/loggingPermission-tf2731649.html#a7619191
Sent from the Logback User mailing list archive at Nabble.com.
November 30th, 2006 - Release of version 0.6
Version 0.6 of logback has been released.
Logback classic now supports automatic configuration, allowing test and production
environment configuration. TurboFilters make their first appearance in a logback
release. They provide ultra-fast filtering possibilities. The logging context now
supports listeners which will be contacted each time the context is reset or started.
SMTPAppender allows for much more flexible configuration than before.
In logback access, new Appenders are available, namely SocketAppender and DBAppender.
Logback access now supports filtering and event evaluations. A CountingFilter has
been added. It provides statistical views of server access, reachable via JMX.
The documentation has also been improved. A complete new chapter has been added about
Appenders, the short introduction to logback classic has been updated and a new
module, containing many configuration examples has been added.
Logback now uses continous integration in its development.
Tests have been improved, many new have been added. This release also provides some
bug fixes.
--
Sébastien Pennec
sebastien(a)qos.ch
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch/
Hello,
I'm new to LogBack and I was wondering why log methods do not have a varargs
version, so that one does not need to construct an array of parameter
objects.
Thanks,
Zohar.
In version 0.5 of logback the logback-access jar file does not contain the
slf4j API, unlike the same jar file of version 0.3. What jar file should I
add in order to be able to migrate to the new version?
--
YF
October 26th, 2006 - Release of logback 0.5
Version 0.5 for all three logback modules is now available.
This release offers a big improvement in Joran. Joran is now able to replay
configuration elements.
Logback's documentation has also been improved. A complete reference on Layouts is
available in the logback manual directory, as well as a FAQ page.
You can download the modules, including full source code, class files and
documentation on our download page, shown below.
http://logback.qos.ch/download.html
You can receive logback related announcements by subscribing
to the logback announce mailing list. To subscribe to logback-announce
list, please visit the following URL.
http://logback.qos.ch/mailinglist.html
--
Sébastien Pennec
sebastien(a)qos.ch
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch/
