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.
Thank you for answer!
It becomes clear for me :)
So the only way to make my objects independent on avalon is create wrapper for Logger interface :(
You can run non-avalon component in Merlin by defining your own contextualization stage handler. This lets you define your own container/component relationship without using any avalon interfaces.
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]