Shibboleth Developers

[Walter Hoehn <>]

So, MDC's don't work for you here?  I'm not against re-analyzing the  
way we do things, and I'm sure there is room for improvement  
specifically in our logging conventions.  However, I really don't  
like the idea of having multiple conventions across the code-base.

-Walter


On Jun 23, 2005, at 10:29 AM, Howard Gilbert wrote:
> [Shibboleth]
>
> Shibboleth code generally followed the "name your logger the same  
> as your class" philosophy. I have attempted to modify this by  
> creating an artificial Logger name hierarchy prefixed by  
> "shibboleth.init" for initialization operations. The objective is  
> to collect messages arising from the setup of parsers and schemas,  
> the parsing of XML configuration file, the loading and  
> initialization of plugins, and so on. Although these things tend to  
> occur first and therefore would be at the beginning of a  
> comprehensive log, there is provision for a configuration file to  
> be reloaded if it changes in the middle of the day. Obviously if  
> you replace the Metadata at 3:00 PM and discover a problem with an  
> IdP at 4:30, it is important that the update not be buried as a  
> couple of lines in the middle of routine request processing. Giving  
> them their own log makes them harder to miss.