Are we actually using the spring.schemas files?

[Cantor, Scott]

I've been investigating the situation with Spring schema lookup using the
attribute resolver unit tests, and I've concluded that at least in the
unit testing case with Eclipse or Maven, the spring.schemas file in the
idp-attribute-resolver-spring module is never used.

Or rather, it's used in the sense that Spring loads it, but it is never
honored. Emptying it out has no effect on the tests.

Moreover, I manipulated the schemaLocation in one of the test files to
reference the URL http://shibboleth.net for one of the schemas, and then I
mapped that to a classpath location, and it didn't change anything, Spring
still tried the http:// location.

I recall that we used to be manipulating the Spring loader such that we
were mis-using the schema mappings file but it didn't matter, but I don't
think we're using a custom DocumentLoader in V3. So I'm a little confused,
something isn't working as it's meant to.

My sense was that rather than try and torture Spring into doing the right
thing, we should just use schemaLocation in the config files to point to
actual http:// locations for editing purposes, and then use spring.schemas
to fix the loading at runtime to be local. But that doesn't seem to work.

-- Scott