You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2005/05/23 04:22:01 UTC
DO NOT REPLY [Bug 33347] -
[logging] Allow logging additional fields to database
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=33347>.
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=33347
skitching@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From skitching@apache.org 2005-05-23 04:21 -------
No existing logging library I am aware of takes parameters for specific pieces
of data such as userid; logging libraries (java.util.logging, log4j, avalon)
just deal in string messages and priorities.
And as commons-logging is intended to be a simple lowest-common-denominator
wrapper over other logging libraries, commons-logging is not the appropriate
place for such features.
I think this problem is best addressed separately from "logging" in the sense
that all the above mentioned libraries use the term.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org