You'd have to catch all the different loggers and funnel them into slf4j. I assume swing uses java.util.logging so you'd want the JUL to SLF4J section of <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://www.slf4j.org/legacy.html">http://www.slf4j.org/legacy.html</a> . In all of my projects I typically include the other bridges (JCL and Log4J) as a matter of course but I normally don't have to deal with JUL.<br>
<br><div class="gmail_quote">On Tue, Feb 23, 2010 at 6:02 AM, Gilles Gaillard <span dir="ltr"><<a href="mailto:gillouxgaillard@wanadoo.fr">gillouxgaillard@wanadoo.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br><br>I'm new to logback and would like to know if the following already exist / is possible, i searched the mailing list but did not find this.<br><br>I've a GUI application performing usual logging through logback (that's ok) and would ensure that any unexpected failure(s) be logged.<br>
For example, unexpected errors occuring on the swing EDT go the std err.<br>Usually I would do this by redirecting the standard out/err streams to some file output. Note also that I would like to ensure that logs from different threads will log properly. For example, stack traces should not be mangled by other logs.<br>
<br>I wonder it is possible to do this through the logback configuration. <br>If not what would be the best way.<br><br>Thanks,<br><font color="#888888">-- Gilles</font><br>_______________________________________________<br>
Logback-user mailing list<br>
<a href="mailto:Logback-user@qos.ch">Logback-user@qos.ch</a><br>
<a href="http://qos.ch/mailman/listinfo/logback-user" target="_blank">http://qos.ch/mailman/listinfo/logback-user</a><br>
<br></blockquote></div><br>