Logging pageflow - In a Hurry...please help :)

Question

Hi guys,
I need to log messages from my pageflow into a log file.
All my pageflows are inside a root package called pageFlows.
my log4j.properties is specifying
log4j.logger.pageFlows=debug, myLogger
log4j.appender.myLogger=org.apache.log4j.DailyRollingFileAppender
log4j.appender.myLogger.DatePattern='.'yyyy-MM-dd
log4j.appender.myLogger.File=C:/myLog.log
log4j.appender.myLogger.Encoding=UTF-8
log4j.appender.myLogger.layout=org.apache.log4j.PatternLayout
log4j.appender.myLogger.layout.ConversionPattern=%d{yyyy-MMM-dd HH:mm:ss,SSS} %5p [%t] (%c{1}) - %m%n
I wouldn't like to use rootLogger, that I know that works. I have tested it. And also wouldn't like to change the workshopLogCfg.xml or, if have to change workshopLogCfg.xml I would like to do the smallest change possible in order to keep using my log4j.properties
How can it be done without altering workshopLogCfg.xml?
and
How can it be done altering workshopLogCfg.xml to use my log4.properties?
I know that to log on pageflows, the logger should be declared as transient, but now almost about to deploy to production this problem has been found and to update all pageflow Loggers to transient would impact in doing lots of regression tests that don't have time to be done.
If I use rootLogger I receive the message log of pageflows, but also receive other undesired messages...so, is also possible to create some exclusion filter to avoid unwanted classes debug information?
Edited by dfcastro at 12/11/2006 3:10 AM

Answer 1

Thanks to everyone who answered my question.
The solution was a servlet that loads up the lo4j.properties on startup using his init method.
With that you don't need to declare the Loggers on pageflows as transient.