I can see where allowing the user to define a property programmatically for a logger would be useful - and the appender could take advantage of this and only call logger.addproperty(xxx,xx) in activateOptions instead of on every append.
-----Original Message----- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2003 12:10 PM To: [EMAIL PROTECTED] Subject: Setting event properties We have recently added properties that can be set per LoggingEvent. Any component having access to an event can programmatically set a LoggingEvent property. Thus, any custom appender or layout or even a pattern converter could set the event property. The question is then whether properties should be set per appender, per logger or per hierarchy? Is per appender enough? Any use cases for event properties set by loggers? or hierarchy wide properties? -- Ceki Gülcü For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp import org.apache.Facetime; ApacheCon US 2003, 18-21 November http://apachecon.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
