Mircea Toma wrote: > > ----- Original Message ----- > From: "Berin Loritsch" <[EMAIL PROTECTED]> > To: "Avalon Development" <[email protected]> > Sent: Tuesday, August 21, 2001 11:50 AM > Subject: Re: LogKitManagement > > > Mircea Toma wrote: > > > > > > Hi, > > > > > > I thought that the purpose of LogKitManagement was to avoid the circular > > > depedencies Avalon<->LogKit. If you still use Configurable, > Loggable..... > > > why not use a ComponentManager/Selector to do the same job? > > > > Because it is the wrong pattern. We don't obtain loggers by > > selecting them (how would we know if we couldn't select the right > > one). > > > > Yes, but targets/categories can be selected isn't it (assuming there is only > one hierarchy)?
It really doesn't matter. Logging is a system level function. It is too much of a core function to go through formal Components. The ComponentManager/Selector approach would require refactoring LogKit to use Avalon Framework hooks, creating a circular dependency. It is the wrong pattern. It's like using a neumatic hammer when all you need is a rubber mallet. Beyond that, the Hierarchy is basically hidden from view with the LogKitManager. It is unnecessary to use it at all. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
