I missed this response, sorry. The problem with this is that I would like to keep the original log message level and other meta-data, essentially using logback as a _filtering engine_ instead of having it generate final log strings. The ConsoleAppender approach logs everything at INFO level, even If the original message was DEBUG level, loosing context for the Glassfish log tooling. So, the JDK14Appender is still warranted and useful. /Thorbjørn From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of cinhtau Sent: 9. februar 2011 17:23 To: logback-user@qos.ch Subject: Re: [logback-user] JDK14Appender for logback: Anybody written one? Thorbjørn Ravn Andersen-4 wrote: In other words, I need a JDK14Appender for logback. This is not necessary. You can define an ConsoleAppender. Everything that points to Console is automatically directed in Glassfish to java.util.logging and server.log. Just add ConsoleAppender and you should accomplish your objective. _____ View this message in context: Re: JDK14Appender for logback: Anybody written one? <http://old.nabble.com/JDK14Appender-for-logback%3A--Anybody-written-one--tp30017964p30884388.html> Sent from the Logback User mailing list archive <http://old.nabble.com/Logback-User-f16252.html> at Nabble.com.