I'd love to be able to do this, also. But log4j doesn't provide a ready-made way to do this. You could write a filter that would examine the call-stack of the LogEvent passed to it, but of course that's quite a performance hit.
--Ian --- Nathan Coast <[EMAIL PROTECTED]> wrote: > Hi > > I have debug statements in core utilities, the problem is that when I > turn debug > on for these components, the volume of debug is too great. Is there > any way to > turn on debug for a component based upon the calling system (package) > as oposed > to the classname of the util component? > > Thanks > Nathan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
