OpenSAML user discussion

["Scott Cantor" <>]

> The library first attempts to look up the unmarshallers by *type* and
> then element name.  There is, and really can't be, an unmarshaller for
> the <Statement> element so it has to rely on types.

What I've done to work around this in C++ is to register a Statement 
implementation that supports the "any" content model. If something supports 
the xsi:type, it gets used, otherwise my stub does.

This isn't strictly correct (Statement is empty, not any), but I think it 
works better in the face of unknown extensions.

-- Scott