On Tue, 5 Feb 2002 10:58, [EMAIL PROTECTED] wrote:
> Had a bit more of a think about the problem and realized that I can write
> my own class to replace DefaultLogKitManager. The sad part is that the only
> code that has to change is in the getLogger method. Everything else is a
> direct copy - pitty about the lack of reuse but this may be easier than
> changing the interface.
Alternatively we could make it easy for you to subclass DefaultLogKitManager
so you only have to overide one method ;) If we added a "getLoggerMap()"
method you could simply do something like
class MyDefaultLogKitManager extends DefaultLogKitManager
{
public final boolean isLoggerDefined(String categoryName)
{
final Logger logger = (Logger) getLoggerMap().get( categoryName );
return ( null != logger )
}
}
does that work?
--
Cheers,
Pete
*------------------------------------------------------*
| Despite your efforts to be a romantic hero, you will |
| gradually evolve into a postmodern plot device. |
*------------------------------------------------------*
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
