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=14155>. 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=14155 Access to underlying native logging provider missing ------- Additional Comments From [EMAIL PROTECTED] 2002-11-01 17:48 ------- But that's my point ... Even if the method you wanted was present, the object you get back would have to be cast to a Log4J Category (or whatever), so that you can configure it. In that scenario, why don't you just ask Log4J to give you a Category instance for exactly the same name? It's supposed to give you the same instance that commons-logging will be wrapping. Therefore, you should be able to access the appropriate Category object without the proposed new method. -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
