commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16039] - Log4J shutdown not invoked?
Date Sun, 30 Mar 2003 23:49:15 GMT
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=16039>.
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=16039

Log4J shutdown not invoked?

craig.mcclanahan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From craig.mcclanahan@sun.com  2003-03-30 23:49 -------
With regard to William's question about "Log4jFactory" being considered part of
Log4J, I am very unhappy to find that it actually got added, since it doesn't
seem to add any useful value, does a half-baked job of pretending to manage the
underlying Log4J stuff, and only obfuscates everything else.  I'm going to be
arguing that it get deprecated in 1.0.x and removed in 1.1.x versions of
commons-logging.

It is said over and over in the documentation, and I'll say it again here --
configuration and management of the underlying logging system is out of scope
for commons-logging, which was originally, and should remain, totally focused on
wrapping the actual logging of messages.  If your application needs to manage
the configuration and cleanup of the underlying logging implementation, it must
do so itself.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message