Shibboleth Developers

[Chad La Joie <>]

On 9/17/10 4:26 PM, Peter Schober wrote:
> * Chad La 
> Joie<>
>   [2010-09-15 14:46]:
> > The latest, and likely final, IdP 2.2 snapshot is available for
> > download[1].  This release is mostly bug fixes and updated
> > libraries.
>
> Is there still logging available for loading (i.e. checking for changes)
> to attribtue-{resolver,filter}.xml?
> I was writing out these events to see when changes to those files will
> be picked up.
>
> With the current snapshot (the first one I tried, so I can only
> compare this to the 2.1.5 release) the only events I see from
> org.opensaml.util.resource.ResourceChangeWatche are for logging.xml.
> I don't see anything related to the other files configured for
> polling.

Thanks for catching this.  The log message was removed from there and 
was meant to be moved to 
edu.internet2.middleware.shibboleth.common.config.BaseService but 
wasn't.  I just checked this in.  It will now log, on info, when the 
service configuration has been loaded initially and when the 
configuration is reloaded.

> Speaking of polling: should values for
> configurationResourcePollingFrequency="300000" also be converted to
> XML Schema duration notation? At lease no warnings were generated for
> these in services.xml.

Yeah, it is a schema duration, and there is a log message it's just 
ending up in your servlet container log file.

When the IdP starts up it installs a very minimal logging configuration 
which outputs any WARN or ERROR message to the STDOUT.  Most containers 
will redirect that to their own log files.  Also, since the logging 
service is a service just like the attribute authority the IdP needs to 
first read the services.xml file before it starts up the logging 
service.  So, it's a chicken and the egg issue.

--
Chad La Joie
http://itumi.biz
trusted identities, delivered