Christopher,
As I wrote already on Feb 17:
There is another aproach, as taken by http://code.google.com/p/log5j/.
It is
a wrapper around log4j. I wish they had made it for SLF4J!
I am still waiting for someone to this for SLF4J. It should not be hard. I did
not yet find the
[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
Yes Erick, I did see your earlier post. And while I do agree that such a
wrapper would be nice, I just wish we could stay away from such extras.
I'm not interested in more clutter/dependencies. I'd like to have the
logging API natively support these things.
-chris
Thanks,
Christopher White
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 annoying to have
to remember to change syntax when logging errors (cannot use paramatized
[EMAIL PROTECTED] wrote:
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 annoying to have
to remember to change syntax when logging
It's nice to see that you were on top of this already.
My only issue with your fix is that it can be ambiguous as to which comes
first (params or exception). I'd much prefer putting the exception at the
front of the method signature (as was suggested by another user in either
this or the
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
[EMAIL PROTECTED] wrote:
It's nice to see that you were on top of this already.
My only issue with your fix is that it can be ambiguous as to which comes
first (params or exception). I'd much prefer putting the exception at the
front of the method signature (as was suggested by another
I tried running a later version of slf4j, but the problem is that I'm running
JBoss AS 4.0 and it has an older version of log4j bundled in it (which I'm
having a heck of a time upgrading). It appears that from version 1.4.0 and on
slf4j requires a newer version of log4j.
Thanks,
Jeff
