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=28237>. 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=28237 [PATCH] Use the commons logging LogFactory also in Fop.java ------- Additional Comments From [EMAIL PROTECTED] 2004-04-19 03:42 ------- 1) why did the Sun guys put setLevel() in the API for java.util.logging? 2) why did the commons-logging guys put setLevel() in SimpleLog? You caught me on the first question--I noticed I was in error when I wrote: " What they (and Sun, with its 1.4 logger) are telling you--logging is a configuration and not a runtime issue--should carry some weight with you. " Sun is *not* telling us this, precisely because they do have a setLevel(). (But that does not necessarily mean they advocate calling programs from switching it--the user could be setting it for his own embedded program.) In the meantime, it may be helpful for you to look at C-L's team's thoughts on having a setLevel() below, and in the last link, a potential workaround as well as Craig McClanahan's concerns with modifying the underlying implementation from C-L: http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=102571996601634&w=2 http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=101096333702331&w=2 http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=101097934025726&w=2 http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=101068848405397&w=2 http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=101061362702721&w=2 (point 2) http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14155 (sample workaround, also Craig's four problems with a setLevel()) Also, to give you a better idea of the usage of C-L, here's a list of the 88 projects currently linking with it: http://lsd.student.utwente.nl/gump/jakarta-commons/commons-logging/index.html#Project+Dependees Glen
