OpenSAML user discussion

["Scott Cantor" <>]

> Yeah, I took a quick look, I haven't looked at the new XACML stuff much
> yet.  These appear to be just simple provider bugs and/or config file
> bugs.  The DescriptionType doesn't have any impl classes, nor a config
> file entry, so when it's unmarshalled, it gets created as the default
> provider (XSAny).  But the parent (PolicyType) doesn't handle XSAny's in
> its processChildElement and so it gets (silently) ignored.

I think I raised that issue a long time ago, but that seems like
questionable behvaior to me. Silently ignoring stuff while ending up with a
distorted tree seems like a bad outcome.

-- Scott