Is this the way it's done in Fortress too? I vaguely remember it passes the LoggerManager in the Context object? I would prefer the way Fortress exposes the LoggerManager for consistency with 2.2.
-- Unico > > -----Original Message----- > From: peter royal [mailto:[EMAIL PROTECTED] > Sent: vrijdag 31 oktober 2003 2:55 > To: [EMAIL PROTECTED] > > On Oct 29, 2003, at 6:41 AM, Vadim Gritsenko wrote: > > No problem at all; for compatibility reasons it makes sense > to revert > > the change. Unico, do you know what change caused this? > > I believe I am the guilty person :) > > In the removal of LogKitManager / LogKitManageable, the > sitemap no longer has a handle to the root LoggerManager, > rather it just creates a LoggerManager based off of its > current Logger. > > This could probably be worked around by putting the > LoggerManager that is passed to the Cocoon class into the > ServiceManager, and thus any component that wants to get the > 'root' LoggerManager for Cocoon can just do > ServiceManager.lookup( LoggerManager.class.getName() ); > > -pete > > >
