http://bugzilla.slf4j.org/show_bug.cgi?id=110
Stephen Duncan Jr stephen.dun...@gmail.com changed:
What|Removed |Added
CC|
http://bugzilla.slf4j.org/show_bug.cgi?id=110
--- Comment #7 from Robert Elliot rob...@teviotia.co.uk 2009-05-17 23:05:29
---
Just returned to this after a break - I have some ideas, but I'm concerned
about the JRE level it should support. I initially wrote this against Java 6.
I tried
http://bugzilla.slf4j.org/show_bug.cgi?id=110
--- Comment #6 from Ceki Gulcu lis...@qos.ch 2009-04-23 16:47:27 ---
(In reply to comment #5)
That was why I rejected that approach - it seems to me that exceptions are the
one thing you really don't want to swallow accidentally or attach
http://bugzilla.slf4j.org/show_bug.cgi?id=110
--- Comment #4 from Ceki Gulcu lis...@qos.ch 2009-04-21 19:25:45 ---
(In reply to comment #3)
The problem I cannot solve is how to work out
when the stack trace has ended and hence when it is time to flush the
aggregated stack trace lines to
http://bugzilla.slf4j.org/show_bug.cgi?id=110
--- Comment #5 from Robert Elliot rob...@teviotia.co.uk 2009-04-21 21:01:33
---
(In reply to comment #4)
Unfortunately, you have to wait for a new log statement to determine the end
of
the throwable which introduces a new latency, which may
http://bugzilla.slf4j.org/show_bug.cgi?id=110
Ceki Gulcu lis...@qos.ch changed:
What|Removed |Added
CC||lis...@qos.ch
