Hi!
I don't understand why Logger interface doesn't extend org.apache.commons.logging.Log interface ?
I think that it's more correctly to use Log interface, wich is supported by all jakarta. In this case we will be able to work with log system in the following way:
class ClassThatNotDependOnAvalon{ protected Log firstLogger; protected Log secondLogger;
}
class AvalonComponent extends ClassThatNotDependOnAvalon implements LogEnabled{
void enableLogging(Logger avalonLogger){
firstLogger = avalonLogger.getChildLogger("first");
secondLogger = avalonLogger.getChildLogger("first");
}
}
Or I missed something?
Conceptually it is close to being possible - however - for the time being commons logging does not separate the api and impl deliverables. This introduces restrictions in terms of what you need to load into classloaders to make things work properly - and in particular this means that the client classloader has to include the logging implementation classes (and that's not desirable).
Stephen.
--
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/merlin/distributions/latest | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
