On Jan 11, 2007, at 19:51, [EMAIL PROTECTED] wrote:
Andreas L Delmelle writes:
log is a protected static, so if the class resides in the same
package, then you can use direct member access. Currently, in some
places, the properties seem to be routing the message to the FO's
logger, instead of u
Andreas L Delmelle writes:
> log is a protected static, so if the class resides in the same
> package, then you can use direct member access. Currently, in some
> places, the properties seem to be routing the message to the FO's
> logger, instead of using Property.log directly...
Or even
On Jan 11, 2007, at 18:31, Andreas L Delmelle wrote:
... use an instance method to access a protected static member of
the superclass. That's a good one! :-)
And what about:
if (log.isDebugEnabled()) { getLogger().debug("..."); }
unless we were thinking about tying the settings for the sta
On Jan 11, 2007, at 13:41, [EMAIL PROTECTED] wrote:
In FONode, it say:
//TODO Remove getLogger() method!
Yet everywhere around the code base it says foo.getLogger(),
in particular for FObj instances. What is the preferred way
to aquire a logger instance?
log is a protected static, so if
