Jukka Zitting wrote:
On Thu, May 28, 2009 at 6:17 PM, Ceki Gulcu c...@qos.ch wrote:
No, just that in most cases some essential piece of the puzzle (source
code, stack traces, or in this specific example thread names) is not
readily available for a variety of different reasons. For example
Thorbjoern Ravn Andersen wrote:
I think that would be one of those use cases for an NDC... see
http://apps.sourceforge.net/trac/lilith/wiki/NestedDiagnosticContext
Interesting. But does anything actually happen when the push and pops
are executed?
You can emulate NDC using MDC. Anyway,
Here is a idea:
Marker TX_BEGIN = MarkerFactory.getMarker(TX_BEGIN);
Marker TX_END= MarkerFactory.getMarker(TX_END);
try {
logger.info(TX_BEGIN, beginning tx);
doSomething();
} finally {
logger.info(TX_END, ending tx);
}
Thorbjoern Ravn Andersen wrote:
Ceki Gulcu skrev:
Thorbjoern
Thorbjoern Ravn Andersen wrote:
Ceki Gulcu skrev:
Here is a idea:
Marker TX_BEGIN = MarkerFactory.getMarker(TX_BEGIN);
Marker TX_END= MarkerFactory.getMarker(TX_END);
try {
logger.info(TX_BEGIN, beginning tx);
doSomething();
} finally {
logger.info(TX_END, ending tx);
}
Ok. If I
Ralph, thank you for catching this.
Ralph Goers wrote:
.reportFailure(Class path contains multiple SLF4J bindins.);
should be
.reportFailure(Class path contains multiple SLF4J bindings.);
Ralph
On Jun 9, 2009, at 1:24 PM, c...@slf4j.org wrote:
Author: ceki
Date: Tue Jun 9 22:24:16 2009
New
June 10th, 2009 - Release of SLF4J 1.5.7
Hello all,
I am happy to announce the immediate availability of SLF4J version
1.5.7, consisting of bug fixes and minor enhancements. It is totally
compatible with SLF4J version 1.5.6.
Please refer to the the news page for precise details.
Hello Thorbjoern,
It's a nice read. I'd like to link to it from the Articles section of
http://slf4j.org/docs.html asap. Please let me know when you are ready.
Thorbjoern Ravn Andersen wrote:
Joern Huxhorn skrev:
Thorbjoern Ravn Andersen wrote:
Would your friend be interested in
Hello all,
My submission for a SLF4J/logback talk for this year's Devoxx
conference has been accepted. For those who don't know Devoxx, rumor
has it that it is the biggest Java conference in Europe.
Cheers,
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for
Comments inline.
Pete Muir wrote:
Hi,
As discussed here https://jira.jboss.org/jira/browse/WBRI-290, we would
like to switch to slf4j as our logger (it offers a logging facade,
supports MDC/NDC and parameter replacement).
However, as Takeshi highlights here
Pete Muir wrote:
This is valid in Java 5 and above. For example:
public interface Logger {
public enum LogMessages {
WRONG_PASSWORD
}
public static class Test {
public void test() {
Logger logger = new Logger() {
public void warn(Enum? message) {
Ralph Goers wrote:
As I've said, I'm not at all in favor of SLF4J doing I18N. It is
better to do it under a framework such as Spring's MessageSource
interface where you can either use the default implementation, which
uses ResourceBundles, or easily provide your own. As I said, I'm also
Ralph Goers wrote:
In cases like event logging it may be that the event logs
are viewed by customer service reps speaking in multiple languages. In
that case the locale of the person viewing the log is important (which
may be days or months after the log entry was recorded).
Very good
Hello all,
Given that git is in my opinion such a clearly better version control
system than Subversion, I migrated the SLF4J svn repository to git. It
was easier than expected.
There are two master repositories, one hosted at git.qos.ch and the
other hosted at github. For more information on
Jukka Zitting wrote:
Hi,
It would be useful to have the old svn branches and tags also
reflected in the slf4j.git repository. If you used the standard layout
option to git-svn when migrating the code, they actually should
already exist as remote branches. Copying the references to normal
I think git supports a whole bunch of protocols including http and/or webdav.
The git.qos.ch server currently supports SSH (port 22) and the git protocol
(port 9418).
Github allows you to fork the repository, but the forked version, as far as I
could tell, is accessible only via the git
Added http support for cloning. See http://slf4j.org/repos.html
Ceki Gulcu wrote:
I think git supports a whole bunch of protocols including http and/or
webdav. The git.qos.ch server currently supports SSH (port 22) and the
git protocol (port 9418).
Github allows you to fork
Takeshi Kondo wrote:
If log level is separated, logging code is
public class enum LogMessages{
@Debug(debug log message)
TEST0001
}
Doesn't LogMessages need to be compiled? If LogMessages needs compiling, how is
it helpful?
--
Ceki Gülcü
Logback: The reliable, generic, fast
Takeshi Kondo wrote:
public class enum LogMessages{
@Debug(debug log message)
TEST0001
}
If I followed you, the idea is to encode the resource bundle *keys* within
enums. You still need to check the consistency of the resource bundle keys,
including copies found in various language
Takeshi's submission is not a finished product so let's go easy on him. While I
have still not bought the idea of levels in enums or resource bundles, I think
the idea of using enums for resource bundle keys is an important step forward.
Having levels in the enum or resource bundles (I
Hi Takeshi,
Thank you for your response. I have looked at your code again and now understand
how levels can be set in resource bundles.
Having said that, I am not convinced that associating levels to keys in resource
bundles is a good idea because there are other possibly better ways of
Takeshi Kondo wrote:
Hi Ceki
The fact that it can't be done in log4j does not mean that it can't be
done.
Is it mean that it can be done in logback?
If it is, I'll change logger to logback.
To be honest, at present time it can't be done in logback either. However,
logback already has
Ralph Goers wrote:
On Aug 24, 2009, at 1:25 PM, Ceki Gulcu wrote:
Takeshi Kondo wrote:
Hi Ceki
The fact that it can't be done in log4j does not mean that it can't
be done.
Is it mean that it can be done in logback?
If it is, I'll change logger to logback.
To be honest, at present
28th of August 2009 - Release of CAI18N version 0.2
I am happy to announce the immediate availability of CAI18N version
0.2. Compiler Assisted Internationalization, abbreviated as CAI18N, is
a java library for writing internationalized messages. CAI18N is spawn
of SLF4J.
The two-page manual
a compile error in MessageIdVerifier. The default JVM on my
machine is 1.5. I guess you don't have a mailing list yet for the project.
Ralph
On Aug 28, 2009, at 6:04 AM, Ceki Gulcu wrote:
28th of August 2009 - Release of CAI18N version 0.2
I am happy to announce the immediate availability
Thorbjoern Ravn Andersen wrote:
added by portage for gitosis-gentoo skrev:
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project SLF4J: Simple Logging Facade for Java.
Could you remove
September 4th, 2009 - Release of SLF4J 1.5.9-RC0
Hello all,
I am proud to announce the immediate availability of SLF4J version
1.5.9-RC), 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
101 - 126 of 126 matches
Mail list logo
