changing xml schema definitions ?

[Tom Zeller]

>>> We actually intentionally stopped using defaults in schemas because it
>>> creates some problems figuring out in the code what's happening. It also
>>> creates problems with signed documents, which is less of an issue here,
>>> but we have config files that we anticipated wanting the ability to
>>>sign.
>>
>>To be clear, the schema is shibboleth-2.0-attribute-resolver-ad.xsd,
>>does that change any the warnings already expressed ?
>
> Not in principal. I don't necessarily expect people to be using signed
> resolver files, but that's certainly a public file we meant to have the
> option to sign, and we definitely deliberately moved away from using
> defaults in those schemas.
>
> If the problem is baking the knowledge into the bean parser(s), I'd rather
> it be in the components themselves and just have them default the property.

Okay, thanks. Will not consider schema defaults as a way to simplify
the spring wiring.