http://bugzilla.slf4j.org/show_bug.cgi?id=110
Summary: Create a bridge between System.out/System.err and SLF4J
Product: SLF4J
Version: unspecified
Platform: PC
OS/Version: Mac OS X 10.3
Status: NEW
Severity: enhancement
Priority: P3
Component: Unspecified
AssignedTo: dev@slf4j.org
ReportedBy: [EMAIL PROTECTED]
Created an attachment (id=46)
--> (http://bugzilla.slf4j.org/attachment.cgi?id=46)
Complete project
On my last project I was irritated by legacy and poorly written code writing to
System.out and System.err, including some third party libraries that I could
not alter. So I thought I'd write a bridge between System.out and System.err
and SLF4J so that I would be able to turn them on and off. Here it is.
I've tried to handle the problem of recursion and allowing logging packages to
still write to the Console. I've also supplied a ServletContextListener to
make it simple to set up in a web application.
There is probably more that can be done around preventing recursion disasters -
possibly throwing an Error? I would also like to explore using the marker I
have attached to stack trace events to suppress the pattern other than the
message itself.
--
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dev mailing list
dev@slf4j.org
http://www.slf4j.org/mailman/listinfo/dev
