[logback-dev] Replacing CallerData class

[Maarten Bosteels]

On Wed, Mar 18, 2009 at 9:38 PM, Ceki Gulcu <ceki at qos.ch> wrote:

>
> I don't see packaging data being part of caller data. If it were, we
> would need configuration code to support this case, which would
> unnecessarily bloat the code. Just as importantly, the user would have
> to know how to enable/disable this feature. It's just not worth the
> trouble.


I agree. I've never been a fan of packaging data, not even in stacktraces.

Maarten

>
>
> If you really needed the packaging data, you would write
>
>  logger.debug("I am interested in package data", new Throwable("");
>
>
>
> Joern Huxhorn wrote:
>
>>
>> Well, I agree with your performance argument but the CPD field of STEProxy
>> doesn't need to be used in the common case.
>>
>> I'd use STEProxy simply to keep the possibility to activate such info on
>> demand, i.e. while debugging but not in production.
>> It could certainly come in quite handy under some circumstances, e.g.
>> while walking the path of jar hell.
>>
>> Joern.
>>
>
> --
> Ceki Gülcü
> Logback: The reliable, generic, fast and flexible logging framework for
> Java.
> http://logback.qos.ch
> _______________________________________________
> logback-dev mailing list
> logback-dev at qos.ch
> http://qos.ch/mailman/listinfo/logback-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://qos.ch/pipermail/logback-dev/attachments/20090318/c397988e/attachment.htm>