So what determines what should be an instance logger and what should be
a static logger? From the original article, they recommend creating the
loggers as needed when logging in a static context. To me, that implies
only instance level loggers are allowed globally to a class. In static
contexts, you should get the loggers on an as needed basis.
Tom
Paul Benedict wrote:
It doesn't have to be an all or nothing game either. Obviously, even
in a shared library, instance loggers are not always appropriate. So
it's definitely on a class by class basis.
Frank W. Zammetti wrote:
FWIW, my opinion would be go ahead and change it... unless someone
can show where it would cause trouble, I'm in the better safe than
sorry camp. I know of a number of instances where I've seen Struts
installed in a shared way, either at EAR-level or something like
Tomcat's shared libs directory... I've never heard any trouble
reported from those cases though to be fair.
I think the performance/memory implications are the only thing that
might stop you from wanting to do this... perhaps some benchmarking
is in order?
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
