> Let's say you want to filter the
> jakarta-commons httpclient package out of your logging,
> EXCEPT when you're calling that package from the section of
> your code that you're currently debugging. That's not
> something you can easily do, because you don't know the
> calling context withou
t me if I am wrong.
>
>
> -Scott Heaberlin
>
>
>
> > -Original Message-
> > From: Paul Smith [mailto:[EMAIL PROTECTED]
> > Sent: Friday, February 06, 2004 4:42 PM
> > To: Log4J Users List
> > Subject: Re: logging in util code
> >
gger log = Logger.getLogger(.class);
then the above solution should work, I believe.
Please corect me if I am wrong.
-Scott Heaberlin
> -Original Message-
> From: Paul Smith [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 06, 2004 4:42 PM
> To: Log4J Users List
> Su
The only way I could think of doing this is in the client code that is
going to call the component, place something in the NDC or MDC to
identify it, and then you can filter it at the appender level for the
component logger.
Of course if you do not have control over the client code, then this is
n
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
