Additional debug loggers ?

[Brent Putman]

On 1/28/15 3:05 PM, Marvin Addison wrote:
>
>
>     <logger name="PROTOCOL_MESSAGE" level="DEBUG" />
>
>
> FWIW, I use this logger _frequently_ to diagnose interop problems,

I don't think we can really change this one in any case.  It's what
we've had and documented since the early days of v2, so that one
probably has to stay as-is IMHO.

Related: do we keep the existing logback.xml on a v2 -> v3 upgrade? If
we do, then we really can't change PROTOCOL_MESSAGE period, it's locked
in I think.

In case it's not obvious, the reason we had and still have that one is
that logging to that comes out of multiple classes - many different
Decoders and Encoders.  So it makes sense to have a conceptual
category.  (Also easier to send to a separate file, it's a lot of output.)

If you have just one class that's going to log to a category, then
there's no reason to do a category other than allowing the possibility
of changing the class name (the -api vs -impl issue).  That's why I was
leaning to getting rid of SAML_PRE_ENCRYPTION, feels like an unnecessary
complication.

Really, this is all about: are logging categories part of an "API" of
sorts?  Not really API, but in the sense of deployers and config files.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20150128/13123fed/attachment.html