jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 42413] - [PATCH] Log Taglib enhancements
Date Fri, 18 May 2007 14:54:09 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=42413>.
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=42413





------- Additional Comments From matthewadams@yahoo.com  2007-05-18 07:54 -------
(In reply to comment #2)
> * The <trace> tag depends on what we decide to do with the Log taglib.

I see one of two options for the <trace> tag:
* get rid of it & stick with lowest common demoninator
* keep it and if the underlying logging framework doesn't support it, just 
redirect it to debug level.

Any thought to making the underlying logging framework configurable between 
log4j, commons-logging, & JDK 1.4 logging?  I haven't looked at it much, but 
the thought occurred to me while writing this comment...

-- 
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: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org


Mime
View raw message