>> So, if I understand this correctly, I would need to do something like: >> Logger logger = Logger.get( "logger" ); >> ComponentBase comp = new ComponentBase(); >> comp.setLoggerRepository ( logger.getLoggerRepository()); >> >> ??? That just doesn't seem right. Seems like I should need to get the >> ComponentBase from somewhere, but not quite sure from where.... >> > > FileWatchdog indirectly extends ComponentBase, you would need to call its > setLoggerRepository method. > > FileWatchdog confiFileWatchdog = new FileWatchdog(); > configFileWatchdog.setFile( log4j_xml_path ); > configFileWatchdog.setLoggerRepository(LogManager.getLoggerRepository ()); > configFileWatchdog.activateOptions();
Ahhh - new I was missing something obvious. Thanks. Works like a charm. >> >> I had no idea that 1.3 was geared to be discontinued altogether. Should >> I >> be abandoning 1.3 completely and revert to 1.2? I see there is still >> active >> dev on 1.3, however, so I am confused. Has there been any dev done on >> 2.0 >> at all? > log4j 2.0 development is in its infancy. The enhanced pattern layout > component prepared from log4j 1.3 sources for log4j 1.2 is being hacked > to flesh out log4j 2.0 concepts and interfaces, but it is not yet > functional. > > Ceki Gulcu who was the prime mover in the log4j 1.3 development has a > competing log framework, logBACK (http://logback.qos.ch/), that is likely > what log4j 1.3 would have become but unshackled from any compatibility > expectations with log4j 1.2. If you really want something log4j 1.3 like > and don't care about log4j 1.2 compatibility, it may be an option. I don't think I need anything critical from 1.3 anymore, so maybe just a rollback to 1.2 will be the best. Thanks again for the help! Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
