Re: [slf4j-dev] svn commit: r1155 - in slf4j/trunk/slf4j-ext/src/main/java/org/slf4j: agent instrumentation

Ralph Goers skrev: XLogger just provides some basic extended methods in a standardized way. I would prefer that rather than use _log.debug you would use XLogger.entry as it makes filtering them easier. Let us come back to that later. In our code we manually add entry, exit, caught,

Re: [slf4j-dev] svn commit: r1155 - in slf4j/trunk/slf4j-ext/src/main/java/org/slf4j: agent instrumentation

Thorbjørn Ravn Andersen wrote: Ralph Goers skrev: XLogger just provides some basic extended methods in a standardized way. I would prefer that rather than use _log.debug you would use XLogger.entry as it makes filtering them easier. Let us come back to that later. In

Re: [slf4j-dev] svn commit: r1155 - in slf4j/trunk/slf4j-ext/src/main/java/org/slf4j: agent instrumentation

Ralph Goers wrote: I'd also like to point that XLogger.enter and exit() method use the TRACE level whereas LogTransformer uses DEBUG. A little consistency is in oder... Either both use TRACE or both should use DEBUG. Obviously, I prefer TRACE for this. Logging with flow tracing

Re: [slf4j-dev] svn commit: r1155 - in slf4j/trunk/slf4j-ext/src/main/java/org/slf4j: agent instrumentation

Ralph Goers wrote: XLogger just provides some basic extended methods in a standardized way. I would prefer that rather than use _log.debug you would use XLogger.entry as it makes filtering them easier. In our code we manually add entry, exit, caught, etc. to everything except simple

[slf4j-dev] [Bug 104] XLogger does not implement Logger

http://bugzilla.slf4j.org/show_bug.cgi?id=104 --- Comment #10 from Ceki Gulcu [EMAIL PROTECTED] 2008-10-03 10:27:22 --- Considering the other methods, dump() seemed out of place. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email --- You are receiving this mail

Re: [slf4j-dev] svn commit: r1155 - in slf4j/trunk/slf4j-ext/src/main/java/org/slf4j: agent instrumentation

Ceki Gulcu wrote: What would be better, if it is possible, is to inject the logging dynamically when needed and completely remove it when not, eliminating any performance overhead at all. Stopping and then restarting the application without the agent does exactly that, no? Do you

[slf4j-dev] svn commit: r1174 - in slf4j/trunk: . integration integration/lib integration/src integration/src/main integration/src/main/java integration/src/test integration/src/test/java integration/

Author: ceki Date: Fri Oct 3 17:44:19 2008 New Revision: 1174 Added: slf4j/trunk/integration/ (props changed) slf4j/trunk/integration/build.xml slf4j/trunk/integration/lib/ slf4j/trunk/integration/lib/junit-3.8.1.jar (contents, props changed)

[slf4j-dev] svn commit: r1175 - in slf4j/trunk: integration slf4j-api/src/main/java/org/slf4j/impl slf4j-jcl/src/main/java/org/slf4j/impl slf4j-jdk14/src/main/java/org/slf4j/impl slf4j-nop/src/main/ja

Author: ceki Date: Fri Oct 3 19:09:11 2008 New Revision: 1175 Modified: slf4j/trunk/integration/build.xml slf4j/trunk/slf4j-api/src/main/java/org/slf4j/impl/StaticLoggerBinder.java slf4j/trunk/slf4j-jcl/src/main/java/org/slf4j/impl/StaticLoggerBinder.java

[slf4j-dev] svn commit: r1176 - in slf4j/trunk: integration integration/src/test/java/org/slf4j slf4j-site/src/site/pages

Author: ceki Date: Fri Oct 3 19:56:46 2008 New Revision: 1176 Added: slf4j/trunk/integration/src/test/java/org/slf4j/Pre154VersionMismatchTest.java slf4j/trunk/integration/src/test/java/org/slf4j/StringPrintStream.java

[slf4j-dev] svn commit: r1177 - in slf4j/trunk/jul-to-slf4j/src: main/java/org/slf4j/bridge test/java/org/slf4j/bridge test/resources test/resources/org test/resources/org/slf4j test/resources/org/slf

Author: ceki Date: Fri Oct 3 20:54:25 2008 New Revision: 1177 Added: slf4j/trunk/jul-to-slf4j/src/test/resources/ slf4j/trunk/jul-to-slf4j/src/test/resources/org/ slf4j/trunk/jul-to-slf4j/src/test/resources/org/slf4j/ slf4j/trunk/jul-to-slf4j/src/test/resources/org/slf4j/bridge/

[slf4j-dev] [Bug 97] Please add isLogLevelEnabled(LogLevel) and log(LogLevel, ...) methods to the SLF4J API

http://bugzilla.slf4j.org/show_bug.cgi?id=97 Ceki Gulcu [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] ---

[slf4j-dev] [Bug 98] SLF4JBridgeHandler does not account for loggers with resourceBundle

http://bugzilla.slf4j.org/show_bug.cgi?id=98 Ceki Gulcu [EMAIL PROTECTED] changed: What|Removed |Added Blocks||103 -- Configure bugmail:

[slf4j-dev] [Bug 103] jul-to-slf4j bridge does not handle resource bundles or parameters correctly

http://bugzilla.slf4j.org/show_bug.cgi?id=103 Ceki Gulcu [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[slf4j-dev] [Bug 103] jul-to-slf4j bridge does not handle resource bundles or parameters correctly

http://bugzilla.slf4j.org/show_bug.cgi?id=103 Ceki Gulcu [EMAIL PROTECTED] changed: What|Removed |Added Depends on||98 -- Configure bugmail:

[slf4j-dev] [Bug 79] NullPointerException in SLF4JLocationAwareLog.debug

http://bugzilla.slf4j.org/show_bug.cgi?id=79 Ceki Gulcu [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] ---

[slf4j-dev] [Bug 76] Endless recursion in Marker. contains in case of recursive Marker hierarchy and Marker that is *not* contained .

http://bugzilla.slf4j.org/show_bug.cgi?id=76 Ceki Gulcu [EMAIL PROTECTED] changed: What|Removed |Added Severity|blocker |normal

[slf4j-dev] 1.5.4?

Hello all, I'd like to soon cut a release for SLF4J 1.5.4. Here is the change summary. - Improvements to documentations as well as fix for packaging problems related to slf4j-ext module. - At initialization time, LoggerFactory will check that the version of the slf4j-binding matches that of

[slf4j-dev] svn commit: r1182 - slf4j/trunk/slf4j-ext/src/main/java/org/slf4j/instrumentation

Author: ravn Date: Sat Oct 4 00:49:33 2008 New Revision: 1182 Modified: slf4j/trunk/slf4j-ext/src/main/java/org/slf4j/instrumentation/LogTransformer.java Log: added log level option, default=info Modified: slf4j/trunk/slf4j-ext/src/main/java/org/slf4j/instrumentation/LogTransformer.java