Hi Korosh, > 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.
In our Phoenix project we are using classes that are in their own libraries and maintained seperately too. But these always construct their own Logger (as suggested by Log4J). This way it all works fine. We have got some classes too that require a Logger for their constructor but there we are able to use the avalon.framework.logger.Logger. > 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? This might be a nice solution. Of course this way you can't exchange the logger implementation (i.e. to JDK 1.4) anymore. But you don't want to of course. :-) So I personally would like such a change too. But of course only as a last resort. Regards, Ole -- Ernst Basler + Partner GmbH Tuchmacherstra�e 47 14482 Potsdam Tel: (0331) 74 75 9-0 Direkt: (0331) 74 75 9-60 Fax: (0331) 74 75 9-90 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
