You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2003/01/23 14:47:55 UTC
DO NOT REPLY [Bug 16360] New: -
Lack of properties on LoggingEvent
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16360>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16360
Lack of properties on LoggingEvent
Summary: Lack of properties on LoggingEvent
Product: Log4j
Version: 1.2
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: Other
AssignedTo: log4j-dev@jakarta.apache.org
ReportedBy: apache@twistedprotein.com
I'm not sure of the motivation for having publicly accessible fields on
LoggingEvent but I'm sure the decision was made for some reason. However, not
having getters for timestamp and priority means that I can't treat the
LoggingEvent like a bean. We have a lot of software components that deal with
beans introspectively and I would like to use the LoggingEvent in a
PropertyTable, but I can't because the LoggingEvent doesn't have a timestamp or
priority property.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>