On Wed, 22 Aug 2001 19:41, Giacomo Pati wrote:
> > I am not sure what you mean by this. The Hierarchy and Logger should
> > create
> > Loggers that don't exist but are asked for. Maybe I missed something in
> > explanation ???
>
> I wasn't sure how to handle the following issue. If a client specifies a
> logger (logger="foo.bar") in a component configuration file which doesn't
> exist the Hierarchy.getLoggerForName will return a valid Logger but IIRC
> that logger will not have any LogTargets set, right?
Sortof. It will have LogTargets but it will be those inherited from parent
logger ("foo"), If "foo" is not defined then it will inherit from root logger.
>Thus I've decided to
> return the default Logger passed in at creation time. The alternative would
> be to raise an Exception to signal "no Logger for that category
> configured".
I would prefer to just return "foo.bar".
--
Cheers,
Pete
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
