On Tue, 13 May 2008, Jonathan Swartz wrote: > In the meantime, I might try to do this myself by creating my own > Appender subclass: > > # My::Log4perl::Appender::File defaults to my preferred layout > and layout.ConversionPattern > log4perl.appender.file1 = My::Log4perl::Appender::File > log4perl.appender.file2 = My::Log4perl::Appender::File > > Do you have a vague idea of how I might approach this? Or is it too > diffiicult, and I should just suck up the repetition until the > inheritance feature? :)
Appenders and layouts are different concepts, so I wouldn't put them into the same class. I'd probably just use a template enginge like the template toolkit, define a Log4perl config file in a meta format and have the template engine expand everything before Log4perl reads in the configuration. -- Mike Mike Schilli [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ log4perl-devel mailing list log4perl-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/log4perl-devel