logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38617] - Support for custom levels without specifying classname
Date Sun, 28 Jan 2007 12:07:45 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=38617>.
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=38617


genman@noderunner.net changed:

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




------- Additional Comments From genman@noderunner.net  2007-01-28 04:07 -------

Really the purpose of the patch is to make editing your log4j configuration
files (with your custom levels) easier for your IT team.  This is not a general
concern.

One big problem with having them created dynamically would be introducing memory
leaks.  The other is compatibility.  I.e. how do levels "leave" the system?

I'm guessing this will never "fly" with the log4j team.  So I suggest that you
approach this in another way.  Make a patch that improves the DOM or .properties
configuration format so that levels can be registered at the top.  Then, when
parsing, the levels can be referenced using a simple name.


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


Mime
View raw message