Shibboleth Developers

[Vishal Goenka <>]

Looks like the resolver schema change in 1.3 version of
shibboleth-resolver-1.0.xsd is incompatible with the resolver.jdbc.xml
example.

Specifically, the element StatementCreator (as reproduced below) does not
define the sub-element <Parameter> used in the resolver.jdbc.xml, rather
defines an <xs:any> sub-element. This was fine in 1.2.x since the
namespace of <xs:any> was "##any", but in 1.3 it is "##other", implying
that the resolver.jdbc.xml must define a different namespace for the
<Parameter> sub-element, which it doesn't.

<xs:element name="StatementCreator" minOccurs="0">
        <xs:complexType>
                <xs:sequence minOccurs="0" maxOccurs="unbounded">
                        <xs:any namespace="##other" processContents="lax"
minOccurs="0" 
                                maxOccurs="unbounded"/>
                </xs:sequence>
                <xs:attribute name="class" type="xs:string"
use="optional"/>
                <xs:anyAttribute namespace="##any" processContents="lax"/>
        </xs:complexType>
</xs:element>
 
I'm wondering what would be the recommended approach?

1. Revert to using "##any" as the namespace for the <xs:any> element in
the 1.3 resolver schema.
2. Define <Parameter> as a valid defined element in the schema
3. Define <new:Parameter> and create "xmlns:new some:namespace" in
resolver.jdbc.xml

I would like to think #2 would be prefered.

Thoughts?
- Vishal