At 03:31 PM 4/15/2004 -0400, you wrote:
Your answer raises another question.
I have a factory that creates (possibly) dozens of instances of my
subclasses. Would your suggestion cause a logger to be created for each
and every instance of a subclass? This would eat resources.
Is there a way to
Your answer raises another question.
I have a factory that creates (possibly) dozens of instances of my
subclasses. Would your suggestion cause a logger to be created for each
and every instance of a subclass? This would eat resources.
Is there a way to use the Logger hierarchy to get around
On Thu, 2004-04-15 at 05:27, Robert Pepersack wrote:
> Hi all.
>
> I have an abstract class that has many subclasses. There are several options:
>
> 1. Declare it in the abstract class using the String name of the abstract
> class. For example:
>
> protected static final Logger logger =
Hi all.
I have an abstract class that has many subclasses. There are several options:
1. Declare it in the abstract class using the String name of the abstract
class. For example:
protected static final Logger logger =
Logger.getLogger("org.happy.Superclass"); // Logger does not have na
