Hello Florian,
You probably don't have 10'000 classes but 10'000 *instances* of a class or a
few classes.
Anyway, you don't have to through a factory because the SLF4J factory will
always return the same instance. Do read [1] for more info on this topic.
[1]
October 29th, 2009 - Release of SLF4J 1.5.9.RC1
Hello all,
I am happy to announce the immediate availability of SLF4J version
1.5.9.RC1, consisting of bug fixes and minor enhancements. It is
totally compatible with SLF4J version 1.5.8. However, the slf4j-ext
module ships with a new package
Hello Dana,
It looks like a logback-classic configuration issue. Try
logger name=org.springframework level=WARN/
in order to filter out messages of level INFO generated by spring.
HTH,
Dana P'Simer wrote:
I am using springframework in an application I am writing and I want to
use SLF4J for
Thorsten Möller wrote:
On Thursday, October 22, 2009 7:32 PM [GMT+1=CET],
Ceki Gulcu c...@qos.ch wrote (with possible deletions):
module so that it copies the source files it needs from the
slf4j-api module. This is pretty easy to do with an Ant target
which you can then add to the Maven
Hello Thorsten,
Sounds great. The easiest approach to integrate your contributions would be to
fork slf4j on github and let us know when you are done so that we can study the
results.
To fork SLF4J, create a user id on github and then go to
http://github.com/ceki/slf4j and click on fork.
name.
Thorsten Möller wrote:
On Thursday, October 22, 2009 4:46 PM [GMT+1=CET],
Ceki Gulcu c...@qos.ch wrote (with possible deletions):
Sounds great. The easiest approach to integrate your contributions
would be to fork slf4j on github and let us know when you are done so
that we can study
Thorsten Möller wrote:
On Thursday, October 22, 2009 5:53 PM [GMT+1=CET],
Ceki Gulcu c...@qos.ch wrote (with possible deletions):
I think git supports Unix symbolic links but not all operating
systems support sym links which makes sym-link in git pointless. I am
not aware of a git equivalent
Hello Scott,
From what you write, it looks like you are using the JDK binding
(slf4j-jdk14.jar) instead of log4j (slf4j-log4j12.jar). See also
http://slf4j.org/manual.html
Scott Selvia wrote:
I have changed my code from Log4J logging to SLF4J and I now my log
files are no longer written to
...@slf4j.org] On Behalf Of Ceki
Gulcu
Sent: Tuesday, September 15, 2009 4:14 PM
To: User list for the slf4j project
Subject: Re: [slf4j-user] SLF4J w/Log4J and Axis2 - No Log File is created
Hello Scott,
From what you write, it looks like you are using the JDK binding
(slf4j-jdk14.jar) instead
attachments.
-Original Message-
From: user-boun...@slf4j.org [mailto:user-boun...@slf4j.org] On Behalf Of Ceki
Gulcu
Sent: Tuesday, September 15, 2009 5:12 PM
To: User list for the slf4j project
Subject: Re: [slf4j-user] SLF4J w/Log4J and Axis2 - No Log File is created
Does rampart use SLF4J
Hello all,
There was a wiring problem in our building (qos.ch) where cal10n,
logback and slf4j projects are hosted. As consequence, our various
web-sites were unreachable for about 12 hours. The issue was fixed
just a few minutes ago with the help of our internet provider.
We are currently
Two bits of information should answer your question.
1) A LocLogger *is* a Logger and can be used as such.
2) When you write
Logger lx = LoggerFactory.getLogger(X);
LocLogger llx = llFactory.getLocLogger(X);
then llx is actually a wrapper around that very lx. (llx wraps that very
John Cherouvim wrote:
Hello Ceki
The code that changed is my dependency's (ehcache) and not my
application code.
I just droped the jar into WEB-INF/lib
Is it possible to make logging work again without having to touch any
code but only via configuration file changes?
Have a look at [1, 2].
Joern Huxhorn wrote:
You should really twitter this ;)
Followed your suggestion. Thanks.
On 10.08.2009, at 19:37, Ceki Gulcu wrote:
Hello all,
If you do not fear being bored out of your skull, you can listen to my
Jazoon 2009 presentation on SLF4J and logback for about 45 minutes
ekkehard wrote:
Ceki Gulcu schrieb:
Joern Huxhorn wrote:
You should really twitter this ;)
Followed your suggestion. Thanks.
I like to retweet
what's your Twitter address ?
Cool. My twitter id is 'ceki'.
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework
Hello all,
If you do not fear being bored out of your skull, you can listen to my
Jazoon 2009 presentation on SLF4J and logback for about 45 minutes,
http://beta.parleys.com/#state=state_playerid=357
You've been warned,
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging
J G wrote:
I am trying to use a 3rd party framework(solr) and have its logging
rerouted to log4j and stored in my log4j.xml file. I am running tomcat
5.5 and have enabled tomcat route all of its logging to log4j which is
working fine. However, I can't get solr(which utilizes
Hello Ari,
It's a known problem with Weblogic. Please see:
http://bugzilla.slf4j.org/show_bug.cgi?id=138
Since only Weblogic seems to suffer from this issue, I am leaving it
open for the time being.
BR
Ari Meyer wrote:
Hi,
I get this warning in my Eclipse console (using WTP to connect
Jeffrey Sinclair wrote:
slf4j-user,
I'm looking to use Markers to supplement the information that is being
logged. Most of the examples I've seen have fixed markers which don't
contain any direct context information, instead they are tags for doing
a fixed enrichment of the log message at
scott.ta...@fuse.net wrote:
Greetings,
NDC in log4j is working great for me. I really don't want this thread to
degrade in to why MDC may be better; I'd like to have this question answered
first.
I was very happy to see it in the slf4j JavaDocs:
http://www.slf4j.org/api/org/slf4j/NDC.html
Hello Thomas,
Configuration is not part of SLF4J. As for the logback configuration, please see
http://logback.qos.ch/manual/configuration.html
HTH,
Thomas Laubscher wrote:
Hi
I tried to migrate fom log4j to slf4j and logback.
I used the migration tool, but this didn't change:
Hello Lorenzo,
Chad is right, SLF4J is just an API. Logback is a better home for a
contribution such as yours. By the way, at Jazoon 2009, I met Aaron
Digulla who had an idea similar to yours. So, it's definitely a good
idea that we will expand upon in logback. I invite you to post your
Hello Wim,
Glad to hear that you could debug the problem on your own. As for other options,
I don't have a better proposal than excluding slf4j-nop.
BR
Wim Deblauwe wrote:
I found the problem. It seems the only location you need to look is your
classpath. Since I am using maven a simple
Just released 1.5.8 fixing the problem.
Ceki Gulcu wrote:
Hello Jean-Luc,
The dependency on slf4j-jdk14 is for testing purposes only. The test
scope was accidentally omitted.
Jean-Luc Geering wrote:
Hi there,
Why is there a new dependency from log4j-over-slf4j to slf4j-jdk14
(which
Hello all,
SLF4J users have been asking for varags support for a long time. See
http://bugzilla.slf4j.org/show_bug.cgi?id=31 for more details. The
plan is to add varags support in SLF4J version 1.6 to be released later
this year, possibly in October 2009.
The idea is extremely simple. We would
Hello Erik,
Thank you for posting an initial implementiation. However, the code is a
contribution from Jim Moore to the log4j project. (You can find in log4j SVN
under the contrib directory). Thus, it implicitly carries the the Apache
Software License.
Also note that Jim's code does not
Hello Papick,
There is no such redirection. However, I think that it would be a fairly useful
addition. Would you enter a bug report in bugzilla asking for this feature?
BTW, getting such redirection right is much tougher than you might think.
Papick Garcia Taboada wrote:
Hi,
I have an API
:31 schrieb Ceki Gulcu:
Hello Papick,
There is no such redirection. However, I think that it would be a
fairly useful addition. Would you enter a bug report in bugzilla
asking for this feature?
BTW, getting such redirection right is much tougher than you might think.
Papick Garcia Taboada
Tom,
It appears that you have misunderstood the purpose of SLF4J. If you
place slf4j-jdk14-1.5.6.jar then slf4j-api will bind with
java.util.logging. Logback will not be used. Only if you place
logback-core.jar and logback-classic.jar on your class path (but not
slf4j-jdk14-1.5.6.jar) will
Hello Tom,
The following mailing list archives which are all mentioned in
http://slf4j.org/mailing-lists.html are searchable:
http://news.gmane.org/gmane.comp.java.slf4j.user
http://marc.theaimsgroup.com/?l=slf4j-user
http://www.nabble.com/Slf4J---user-f13203.html
Hi Joern,
You are not beating a dead horse. There is no NDC in SLF4J because it is thought
that the MDC offers a better more general solution than the NDC.
However, I don't understand what you mean when you write:
slf4j.NDC(Parameter is {}., obj)
What does the NDC offer that the MDC does
Hello all,
We just upgraded our server. Testing whether the mailing still works.
Cheers,
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
___
user mailing list
user@slf4j.org
Hello,
I just submitted a proposal for log4j natively implementing the SLF4J
API [1]. Please chime in with your comments on the log4j-dev list if
you are interested in the topic.
[1] http://marc.info/?l=log4j-devm=122830448725216w=2
--
Ceki Gülcü
Logback: The reliable, generic, fast and
of StatusListenerConfigHelper.installIfAsked() I would
say you should assume the property is not defined if you cannot access it.
Gili
Ceki Gulcu-2 wrote:
Gili, Thank you for your message.
I suggest opening a jira issue about this problem. Attaching a test case
to
reproduce this problem would be very
Hello,
SimpleLogger just drops requests of level TRACE and DEBUG. There is no option
to
enable logs of level TRACE and DEBUG using SimpleLogger.
HTH,
dju` wrote:
dju` a écrit :
Hello,
I wonder why DEBUG and TRACE are disabled with the SimpleLogger. In my
opinion, this logger is useful
Hello Raymond,
Raymond Cramer wrote:
I'm new to slf4j, having been using log4j. I am trying to use a
package (netcdf) that requires slf4j, but am having problems getting
my head around some of this stuff.
1) If I have an application (which uses log4j) deployed through
Tomcat, do I
. Assuming
we have done a good job preserving SLF4J backward compatibility, this should
work.
2) leave nlog4j.jar. You then need to remove log4j.jar *and* recompile your
application against nlog4j.jar.
HTH,
Ceki Gulcu wrote:
Hello Raymond,
Raymond Cramer wrote:
I'm new to slf4j, having been
Hello Srinivasan,
The logger.isEnabledFor(...) operation takes about 25 nanoseconds with log4j and
about 10 nanoseconds with logback. new InterpolatedMessage probably takes
longer
than that..
Srinivasan Raguraman wrote:
When we are using log4j as underlying logger, sl4j actually does double
Mads Pultz wrote:
Hi again,
I checked out the source and build a snapshot and could not get it to work.
I found out that the implementations of the getInstance methods do not match
the signature of the corresponding log4j methods. The should return a
Category object, not a Logger. I will
Hello Mads,
Mads Pultz wrote:
That sounds perfect! I noticed that the current svn content only includes
the getInstance() methods. Do you have any plans on implementing the other
deprecated methods? See
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Category.html
for
As similar request has been made by Michael Rumpf in bug 95.
http://bugzilla.slf4j.org/show_bug.cgi?id=95
The getInstance() methods were added recently in SVN. You can expect these
methods to be part of the next release.
HTH,
M. Hansen wrote:
Hi,
We have decided to use JDK1.4 logging
Matt Humphreys wrote:
Hi Ceki,
slf4j hosting sounds good - if you can set me up with access that
would be great. A few questions:
- Are there any guidelines/restrictions for slf4j projects? (e.g.
maven, java version).
SLF4J uses Maven, so for the sake of consistency Maven would be good.
Hi Holger,
Thank you for checking that this bug was fixed in the latest SVN commits.
I'll shortly make a new release, namely 1.5.2, fixing this bug.
Holger Hoffstaette wrote:
On Fri, 06 Jun 2008 03:31:09 +0200, Holger Hoffstaette wrote:
On Thu, 05 Jun 2008 23:53:47 +0200, Ceki Gulcu wrote
[EMAIL PROTECTED] wrote:
Ceki,
I do understand your reasoning, and thank you for your quick response.
And since Logback natively implements SLF4J, its API will also not be
changed to include any new JSE 5 features, correct? Nor will new method
signatures specific to just Logback be
Hi Joern,
Christopher White's sums the warts in the SLF4J API pretty well:
I did know that I can parameterize up to 2 parameters, which is
nice. But I also think that it is annoying to have to remember to
change the syntax once you hit 3+ parameters. Along with this, it is
also
Hello Yannick,
Please see the section jcl104-over-slf4j.jar should not be confused
with slf4j-jcl.jar in the user manual [1]. It looks like you are
deploying jcl104-over-slf4j.jar and slf4j-jcl.jar at the same time.
HTH,
[1] http://www.slf4j.org/manual.html
Yannick PIERSON wrote:
Hi,
I
Hello Udo,
The log4j adapter in the slf4j-log4j12 module does not use renderers on account
of simplicity. More importantly, given that all printing methods in
org.slf4j.Logger take String as their message argument, it does not make sense
to call a renderer on a message of type String.
Thus, I
February 26th, 2008 - Release of SLF4J 1.5.0
I am happy to announce the immediate availability of SLF4J version
1.5.0.
A tool called SLF4J Migrator now ships with SLF4J. It can help you
migrate your project using JCL or log4j to use the SLF4J API.
This release fixes quite a number of bugs.
Hello Ian,
I've created a bug report to deal with this bug. Thank your for the thorough
analysis of the problem.
Ian Carr wrote:
I have noticed significant delays in processing in certain areas and running
the application under a profiler the hotspot is Throwable.getStackTrace,
called
Maarten Bosteels wrote:
Are you saying that we shouldn't expect a release of 1.5 in February ?
No, the milestone release offers an immediate (as in today) solution to the
dependency issues you are facing with SLF4J. I hope to make a release by the
end
of this week but might miss that
Maarten,
I just released 1.5.0-M0 to our repository which is synchronized with ibiblio
(the world-wide Maven2 repository). It should be available in a few hours.
--
Ceki Gülcü
___
user mailing list
user@slf4j.org
Hello Chris,
Given that SLF4J is intended for use by all sorts of libraries, the dependency
graph between libraries and SLF4J can be complex. In particular, it would not
be
unusual for the dependency graph to have multiple dependencies on SLF4J with
*different* versions. Thus, we have to be
Maarten Bosteels wrote:
Hello Ceki,
I started coding a BasicMDCAdapter that could be used by java.util.logging
Had a look at the log4j MDC implementation and also at LogbackMDCAdapter
code.
Currently my implementation is roughly the same as the LogbackMDCAdapter
without the generics
Maarten Bosteels wrote:
I understand. It's not something that has to be decided right way IMO.
But we could already include the attached BasicMDCAdapter in SLF4J
(without the formatter).
That way people using slf4j-jdk14.jar can also benefit from the MDC
with java.util.logging.
And we
Hello Guy,
As implied by both Simon and Jake's answers, the SLF4J is not responsible for
formatting the logs. SLF4J merely delegates to the underlying API, be it log4j,
JUL or logback.
It is entirely possible for the underlying logging API to *conditinally* omit
outputting a line separator
Hello all,
On the Tapestry mailing list there is an interesting discussion about a probably
quite fundamental use case for marker objects.
http://www.nabble.com/T5%3A-Logging-to14622287.html
Cheers,
--
Ceki Gülcü
___
user mailing list
Hi Lowell,
This is a well-known shortcoming of the SLF4J API. However, since exceptions
are
by definition rare, you can write
LOG.debug(Got a +e.getClass().getName()+ with value + e.getValue(), e);
with an *infrequent* loss in performance. Of course, this form is also less
pleasant to
Hello Barb,
The license on those files would be exactly the same as the license on all the
other SLF4J files, namely the MIT license.
I hope this meets the requirements of your review.
Barb Cochrane wrote:
Hello,
There has been interest expressed in using SLF4J 1.4.3 (API and Log4J in
Hi Franck,
Are you using a recent version of slf4j-over-slf4j? Anyway, you can enter this
as a bug report and I'll look into it asap.
Franck Routier wrote:
Hi,
I am trying to use log4j-over-slf4j to get rid of log4j jar and config
files, while using a library that depends on log4j.
But
Writing good log messages is a bit like writing good code. You may encouter
wild
variations in quality as well as style.
Anyway, my suggestion would be to go over the logs which each developer and
show
them better ways of coming up with informative log messages, on a case by case
basis. With
Hello,
Which slf4j binding are you using? Is it slf4j-simple?
Jipeng Tan wrote:
[snip]
Sadly, the output only have the information with log.info
http://log.info, nothing about logger.debug, and the output of
(logger.isDebugEnabled()) is also false, can anyone tell me how to use
debug???
OK. It drops log requests of level DEBUG but prints INFO and above on the
console. The slf4j-simple binding cannot be configured.
Jipeng Tan wrote:
slf4j-simple;
On 10/19/07, *Ceki Gulcu* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
wrote:
Hello,
Which slf4j binding are you
Hi Maarteen,
Comments inline.
Maarten Bosteels wrote:
Hello Ceki,
I started coding a BasicMDCAdapter that could be used by java.util.logging
Had a look at the log4j MDC implementation and also at LogbackMDCAdapter
code.
Currently my implementation is roughly the same as the
Hi Maarteen,
Comments inline.
Maarten Bosteels wrote:
[snip]
But unfortunately, not all SLF4J implementations (or adapters) support
the MDC mechanism.
Indeed.
Would it be acceptable to add basic MDC support to JDK14LoggerAdapter ?
Yes, it would.
The MDC would store its key/value pairs
Thanks for the information.
On a different register, I was quite impressed by Xfire. Is CXF as good?
Christopher Moesel wrote:
Hi Ceki,
I found my problem-- the CXF project had a reference to slf4j-jdk14 version
1.3.1 in one of their POMs. So, it came in as a transitive dependency. As
PROTECTED] On Behalf Of Ceki Gulcu
Sent: Thursday, September 27, 2007 1:35 PM
To: User list for the slf4j project
Subject: Re: [slf4j-user] java.lang.IllegalStateException: Level number 20 is
not recognized.
Thanks for the information.
On a different register, I was quite impressed
Hi Chris,
Several constants defined in the org.slf4j.spi.LocationAwareLogger interface
had
their values changed in SLF4J version 1.4.0.
It looks like a library you are using was compiled with SLF4J 1.3.1 and had the
aforementioned constants folded into its .class file.
Was the version of
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ceki Gulcu
Sent: Tuesday, September 25, 2007 2:55 PM
To: User list for the slf4j project
Subject: Re: [slf4j-user] java.lang.IllegalStateException: Level number 20 is
not recognized.
Looking at the problem
Hi Dave,
There is a known issue [1] with Tomcat version 5.5.15 to 5.5.17. I suggest to
test with a more recent version of Tomcat, say 5.5.19 or later.
Let us know if changing the Tomcat version works for you/
[1] http://bugzilla.slf4j.org/show_bug.cgi?id=15
Dave Golombek wrote:
I'm running
Dave,
I see better now. There is probably a copy of commons-logging.jar somewhere in
Tomcat's class loader hierarchy. Anyway, as the messages indicates the problem
merits a mere warning without further consequences.
If the warning message is too irksome, I suggest that you file a bug report or
Paul,
Have you read the Jboss' documentation on logging [1]?
In particular, are you doing anything special to modify JBoss' classloading
behavior?
[1] http://docs.jboss.org/process-guide/en/html/logging.html
Cheers,
Paul Oswald wrote:
I'm going to give some background information here but
August 20th, 2007 - Release of SLF4J 1.4.3
I am happy to announce the immediate availability of SLF4J version
1.4.3.
Fixed bug 60 as reported by Costin Leau. OSGI manifest entries now
declare the correct SLF4J version.
Clarified the behavior of the various methods methods in the MDC class
with
Hello Arthur,
Thank you for your message. While I'd like to add a binding for log4j 1.1, the
time spend into developing and maintaining this new binding would eat into
higher priority items.
Nevertheless, I'd be happy to reference such a binding if your friend decided
to
write it.
Best
Hi Costin,
Sorry about the hassle. This will be fixed in SLF4J 1.4.3.
Cheers,
Costin wrote:
Hi,
I've noticed that the last release still is marked as 1.3.1 inside the OSGi
manifest entries.
Please update them as well since they are crucial when running multiple jar
versions on the same
Hi Costin,
I hope to release SLF4J version 1..4.3 some time next week.
Cheers,
Costin wrote:
No problem. Slf4j has saved us a lot of trouble and being OSGi-aware is just
superb.
Any idea on what's the ETA of slf4j?
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible
July 12th, 2007 - Release of SLF4J 1.4.2
I am happy to announce the immediate availability of SLF4J version
1.4.2.
The log4j-over-slf4j module has been moved back into SLF4J.
Originally, this module was part of SLF4J and was moved into logback
due to the lack of MDC support in SLF4J. With
Hi Norval,
I am glad to have helped.
Norval Hope wrote:
Ok, you were right - the shared Layout was the root of both evils. As
they say, never argue with the master!
I am attaching the reworked testcase which now works in case it's of any
interest to anyone. I was also hoping someone
July 4th, 2007 - Release of SLF4J 1.4.1
I am happy to announce the immediate availability of SLF4J version
1.4.1.
SLF4J now supports Mapped Diagnostic Contexts (MDC) as requested by
Andy Gerweck and Steve Ebersole in bug 49.
Fixed bug 53 as reported by Heinrich Nirschl. The public method
Please let us know how it goes.
Costin wrote:
Thanks! I'm looking forward to trying it in Spring/OSGi.
It's nice to see that new features get quickly released.
Ceki Gulcu-2 wrote:
May 16th, 2007 - Release of SLF4J 1.4.0
I am happy to annonce the immediate availability of SLF4J
Please let us know how it goes.
Costin wrote:
Btw, do you have any idea when the new 1.4.0 will published into the maven
repository?
Thanks.
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
April 15th, 2007 - Release of SLF4J 1.3.1
I am happy to annonce the immediate availability of SLF4J version
1.3.1.
This release consists of a bug fix and a minor enhancement.
Fixed a silly but nonetheless annoying bug where log request of level
ERROR made through jcl104-over-slf4j would log
81 matches
Mail list logo
