On Mon, 22 Apr 2002 17:40, [EMAIL PROTECTED] wrote: > I propose 3 possible solutions to implement the above:
I count 4 ;) > (1) change the constructors so that a new property "boolean createNew" is > available; > (2) add a property to allow the setting/getting of the property; > (3) subclass the sucker to provide classes that provide the 2 different > behaviours (create a new one or return an null/exception); and/or > (4) pass in a boolean createNew when requesting the logger My suggestion would be instead to add a new method something like the following (maybe with a better name) boolean isLoggerDefined(String name) As that makes it easier from a usability perspective IMO. The main reason for this is that definition of a logger effectively means all child categorys are also usable. Thus if I define "network" logger then I expect to get back a valid logger if I look up "network.interceptor" -- Cheers, Peter Donald -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
