<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Ceki,<div><br></div><div><br><div><div>On 30 Jul 2009, at 14:45, Ceki Gulcu wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>my recommendation would be to ignore the<br>logging separation issue by delegating it to SLF4J.<br><br></div></blockquote><div><br></div><div>I intend to - the problem I'm trying to solve is that the webapp which replaces System.out will replace it with an instance of a class loaded by that webapp's classloader, which will load SLF4J and whatever binding it is loading. So which ever web app is the last to replace System.out will get all System.out calls in all webapps (and indeed in the app server) redirected to the logging system specific to that webapp. Which isn't what I want. I've got a theory about it, hopefully I can get something working soon and show it, as real code is a better basis for discussion.</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>Yes, as far as I know, the app server will set the web app specific<br>class loader for the current thread. <br></div></blockquote><div><br></div>Great, thanks.<br><blockquote type="cite"><div>As for your goal, most application servers have their own way of<br>capturing and redirecting the console. So you may be facing a big<br>hurdle in order to get an app server to adopt your library.<br></div></blockquote><div><br></div>Oh, I'm not aiming that high! Just to allow the writer of a webapp to configure where System.out goes without it screwing up every other webapp deployed on the app server.</div><div><br><blockquote type="cite"><div><br>Anyway, is it correct to assume that you wish to tackle bug 110 [1]<br>outside SLF4J?<br></div></blockquote></div><br></div><div>No, I'd still like to donate it if you want it - just life has got in the way, I've embarked on a fairly major refactor and encountered issues like the one described above and a classloader memory leak that would mean anyone using the library and redeploying the webapp dynamically would have got PermGen issues. I've got another idea about the exception handling issue, too. Hopefully have something out soon.</div><div><br></div><div>Rob</div></body></html>