Hi, I'm trying to figure out a good logging pracise for:
* objects instantiated by factories * objects which are not avalon components * inner classes in avalon components etc. The responsibility for creating the objects above are inside avalon components, thus they have access to the logger created for themselves during merlin startup. What I would like to do, is to add the non-avalon components to the logging framework and have the opportunity to change the logging setting per object, just like one can do with the actual avalon components. I'm thinking about some different alternatives: 1. Instantiate a new logger for an object and add it to the logger hierarchy inside the avalon component (Most preferable) 2. Create a separate logging framework for non-avalon components 3. Use the logger assigned to the avalon component (least feasable) Do you have any other suggestions? How do you handle logging for your non-avalon objects? Tobias Extraction from another thread: ---8<------8<------8<------8<------8<------8<------ >> 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.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
