[slf4j-dev] [Bug 110] Create a bridge between System.out/System.err and SLF4J

[bugzilla-daemon at pixie.qos.ch]

http://bugzilla.slf4j.org/show_bug.cgi?id=110





--- Comment #9 from Robert Elliot <robert at teviotia.co.uk>  2010-03-08 22:36:36 ---
Work on this continues at http://github.com/Mahoney/slf4j.git.  It is now code
complete, with 100% unit test coverage; it is however crying out for some
decent testing in common servlet containers and J2EE application servers, so
that's next on my to-do list.  It also needs documentation, both Javadoc and a
user guide.

The major changes are:

* No longer causes a classloader memory leak - you can apply this library
within a web application that supports context reloading and reload the context
to your heart's content without getting the dreaded PermGen out of memory
error.

* So long as the servlet container/application server sets the Thread's context
class loader correctly, the same SLF4J implementation as is used in the rest of
the servlet context will be used by System.out.  So two servlet contexts (wars)
deployed in the same servlet container with child first class loading and an
SLF4J implementation in each lib folder will see logging output directed
appropriately.

* So long as the servlet container/application server sets the Thread's context
class loader correctly, System.out/err can be redirected to SLF4J in one
servlet context and not in another and in the latter case calls to
System.out/err will still reach the console

* The levels for out and err are now configurable (defaults to out -> info, err
-> error)

* The strategy used to print stacktraces is now injectable via a simple to
implement interface (defaults to logging one line per stacktrace line)


-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.