I am using Log4j for logging a Phoenix SAR app.
In the process of avalanozing my application, I notice that some of my dependent classes that are in their own libraries and maintained seperately required Log4j.Logger as constructor. I implement LogEnabled and will be using the org.apache.avalon.framework.logger.Logger and subsequently the org.apache.avalon.framework.logger.Log4jLogger class. I'd like to avoid maintaing two different Logger classes in my Service class but I see no choice. My client library classes requires Log4j Logger as constructor. Looking at framework's Log4jLogger I notice there are no public accessors to get the log4j's Logger. i.e.: //underlying implementation private final org.apache.log4j.Logger m_logger Short of hacking that into the Log4jLogger and continue to maintain the difference from Apache, does anyone have a suggestion to deal with this? thanks k. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
