OpenSAML user discussion

[Scott Cantor <>]

> FWIW: I've also seen this error at some point, I believe when unittesting my 
> code, *after* adding a parameter to the jvm to endorse xalan/xerces.

No, it happens when you *don't* endorse xalan.

Whenever people say "I endorsed it" and this error comes up, we know they're 
wrong. Might be impossible to figure out why, but it's still true.

> I ended up just disabling the SAML component (as it wasn't neccessary for this
> particular set of scripts anyway), so this won't help you much. The same
> component works fine in production (running in a servlet container which
> endorses xalan/xerces), however, so I'm pretty sure the validity of the XML 
> isn't the root of the problem.

No, it's the lack of validity of Sun's broken XML code that's the root of 
the problem. The XML is fine, and the error message is clearly nonsense.

> I'd also be interested in finding out what the cause of and the solution for 
> this problem is.

Endorse xalan and it goes away.

-- Scott