XML validation problem in apache when upgrading SP from v2 to v3

[Cantor, Scott]

> That's precisely what I did - there were no warnings remaining when I changed
> the namespace declarations apart from the general "DEPRECATED: legacy 2.0
> configuration, support will be removed from a future version of the software".
> Even in the 1,853 log lines when the XML Tooling log level is turned up to
> debug, there is nothing there. And I get the same lack of any warning if I restart
> shibd with the declarations changed to 3.0 - it's apache which isn't happy. And
> mod_shib in apache doesn't log anything when reloaded with the declarations
> set at 2.0.

The RequestMap plugin happens to be a mod_shib only plugin, so if it's not failing to validate, the issue is just deferred to a runtime check for the root element and its namespace and it's obviously wrong. When it says conf:RequestMapper, it's implying that conf has to be bound to the generally enclosing namespace of the file that’s used. It doesn't literally mean the string conf:RequestMapper is required.

-- Scott