commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27663] New: - [logging] Add MemoryLog
Date Mon, 15 Mar 2004 13:48:17 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27663>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27663

[logging] Add MemoryLog

           Summary: [logging] Add MemoryLog
           Product: Commons
           Version: 1.0.4
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Logging
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: joerg.schaible@gmx.de


Statistics show, that logging code take normally nearly 4% of the 
application's code. To increase coverage and exclude side-effects from the 
logging code it is useful to have unit tests running the compete logging code, 
too. The MemoryLog class is especially designed for this purpose, since every 
log entry can be retrieved later on as big list with each entry represented by 
a bean. This makes it e.g. easy to test for thrown and logged exceptions.

Code for MemoryLog and MemoryLogTest attached, code borrows from SimpleLog.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message