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 Tue, 14 Feb 2006 17:30:52 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





------- Additional Comments From carnold@apache.org  2006-02-14 18:30 -------
Okay, I missed that you were expecting the caller to have registered "NOTICE" by creating
a derived 
class prior to calling the configurator and misread the casts of the Priority.INFO et al which
led me to 
think you might have been working on code where Priority extends Level instead of vice-versa.
 

I'm concerned that the lazy initialization of the hashtable might present a threading issue.
 It also 
continues to perpetuate the subclassing Level just to work around the protected constructor.
 I also 
don't like joining the construction and registration actions (though I understand why those
were done).

The NAME#classname is a bit ugly, but it does not require registration of the level prior
to the 
configuration and it only uglifies the configuration file and the benefit of the patch doesn't
seem to be 
sufficient to justify the potential ramifications (particularly in the 1.2.x branch) in my
opinion.





  

-- 
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