Metadata Aggregator schema validation and logging

[Patrik Schnellmann]

On 28.11.11 15:20, Chad La Joie wrote:
> Oh, this is one of those "damned if you do, damned if you don't"
> things.  One of the biggest gripes about the current schema validation
> the IdP does is that it uses classpath URLs.  Probably the easiest way
> to do this is to teach the JVM to resolve classpath: URLs via the
> custom protocol handler provided here (thanks to whoever provided
> this)[1], see Step 3.
Thanks for that.

>> The second thing is logging. I wanted to log less than on debug level, i.e.
>> on the info level which of the EntityDescriptors (or EntitiesDescriptors)
>> were processed. I defined the bean as follows:
>>>     <util:list id="infoStatusClass">
>>>         <value>#{T(net.shibboleth.metadata.InfoStatus)}</value>
>>>     </util:list>
>>>     <bean id="logItemInfo"
>> class="net.shibboleth.metadata.pipeline.StatusMetadataLoggingStage"
>>>           p:id="logItemInfo" p:selectionRequirements-ref="infoStatusClass"/>
>>
>> ... and then used that bean in a stage, but there was no output at all. Does
>> any stage set that info and does that configuration "read" it correctly?
> 
> I'm not sure what you mean here.  What you have there should log, on
> INFO level, anything StatusInfo messages that appear on any element in
> the item collection being processed by that stage.  Are you saying the
> StatusInfo messages are being logged on debugged?  Or that you're not
> seeing any StatusInfo messages at all where you excepted to?  Or
> something else...
I don't see any StatusInfo messages at all on log level INFO.

> [1] https://wiki.shibboleth.net/confluence/display/SHIB2/IdPDevCustomExtension

-- 
SWITCH
Serving Swiss Universities
--------------------------
Patrik Schnellmann, Software Engineer
Werdstrasse 2, P.O. Box, CH-8021 Zurich, Switzerland
phone +41 44 2681559, fax +41 44 2681568
patrik.schnellmann at switch.ch, http://www.switch.ch