<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 12px;">It's still moving - see branch at <a href="http://github.com/Mahoney/slf4j.git">http://github.com/Mahoney/slf4j.git</a> under </span></font><span class="Apple-style-span" style="font-family: helvetica, arial, freesans, clean, sans-serif; line-height: 26px; "><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 12px;">sysout-over-slf4j. It's close to code complete but there's some tidy up and test coverage I wanted to beef up and I wanted to review the Javadoc before updating the bugzilla entry (and I need to get round to printing and signing the form saying I've given it freely).</span></font></span><div><font class="Apple-style-span" face="helvetica, arial, freesans, clean, sans-serif"><span class="Apple-style-span" style="line-height: 26px;">It should be trivial to compile it (mvn package) and the only runtime dependency is slf4j-api. It will require you to add the following line somewhere early in the application's startup sequence:</span></font></div><div><font class="Apple-style-span" face="helvetica, arial, freesans, clean, sans-serif"><span class="Apple-style-span" style="line-height: 26px;"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; ">org.slf4j.sysoutslf4j.context.SysOutOverSLF4J.sendSystemOutAndErrToSLF4J();</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><font class="Apple-style-span" face="Helvetica, arial, freesans, clean, sans-serif" size="3"><span class="Apple-style-span" style="font-size: 12px;">I'd be interested in any feedback as to how it behaves in the wild.</span></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><font class="Apple-style-span" face="Helvetica, arial, freesans, clean, sans-serif" size="3"><span class="Apple-style-span" style="font-size: 12px;"><br></span></font></div></span></font></div><div><div><div>On 23 Feb 2010, at 12:07, Ceki Gülcü wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hello Gilles,<br><br>If as Nikolas suspects, swing uses java.util.logging which it probably<br>does, then go with his suggestion of redirecting j.u.l. to SLF4J.<br><br>If for some reason swing actually writes directly to the console, then<br>you would want to capture system.out and direct it to SLF4J. Robert<br>Elliot started working on this very tricky topic and made some real<br>progress, see [1]; but for some unfortunate reason the issue got stalled.<br><br>HTH<br><br>[1] <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=110">http://bugzilla.slf4j.org/show_bug.cgi?id=110</a><br><br>On 23/02/2010 12:51 PM, Nikolas Everett wrote:<br><blockquote type="cite">You'd have to catch all the different loggers and funnel them into<br></blockquote><blockquote type="cite">slf4j. I assume swing uses java.util.logging so you'd want the JUL to<br></blockquote><blockquote type="cite">SLF4J section of <a href="http://www.slf4j.org/legacy.html">http://www.slf4j.org/legacy.html</a> . In all of my<br></blockquote><blockquote type="cite">projects I typically include the other bridges (JCL and Log4J) as a<br></blockquote><blockquote type="cite">matter of course but I normally don't have to deal with JUL.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Tue, Feb 23, 2010 at 6:02 AM, Gilles Gaillard<br></blockquote><blockquote type="cite"><<a href="mailto:gillouxgaillard@wanadoo.fr">gillouxgaillard@wanadoo.fr</a> <<a href="mailto:gillouxgaillard@wanadoo.fr">mailto:gillouxgaillard@wanadoo.fr</a>>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Hi,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> I'm new to logback and would like to know if the following already<br></blockquote><blockquote type="cite"> exist / is possible, i searched the mailing list but did not find this.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> I've a GUI application performing usual logging through logback<br></blockquote><blockquote type="cite"> (that's ok) and would ensure that any unexpected failure(s) be logged.<br></blockquote><blockquote type="cite"> For example, unexpected errors occuring on the swing EDT go the std err.<br></blockquote><blockquote type="cite"> Usually I would do this by redirecting the standard out/err streams<br></blockquote><blockquote type="cite"> to some file output. Note also that I would like to ensure that logs<br></blockquote><blockquote type="cite"> from different threads will log properly. For example, stack traces<br></blockquote><blockquote type="cite"> should not be mangled by other logs.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> I wonder it is possible to do this through the logback configuration.<br></blockquote><blockquote type="cite"> If not what would be the best way.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"> Thanks,<br></blockquote><blockquote type="cite"> -- Gilles<br></blockquote><br>_______________________________________________<br>Logback-user mailing list<br><a href="mailto:Logback-user@qos.ch">Logback-user@qos.ch</a><br>http://qos.ch/mailman/listinfo/logback-user<br></div></blockquote></div><br></div></body></html>