Shibboleth Developers

["Scott Cantor" <>]

> I tried putting the xerces jar files in "shared/lib" instead of
> in "common/endorsed" - at request of some system maintainers.
> That didn't work.  I got

You're hitting some combination of bugs and potentially errors in your
config file, and it's hard to diagnose given the unpredictable code mix
you're running. As I said before, if you endorse Xerces with the schemas
you've got, it's not even successfully using them at all.

I'd suggest you wait for a complete resolution to this and then refresh your
code completely once a new build is up. It's just too confusing otherwise.

The end result is going to be endorsement though, for reasons that will be
discussed during the call. Using shared/lib is a simple classpath addition,
but endorsement is not. And Xerces will not fully override Sun's code to fix
the memory leak without endorsement at this point due to bugs in Xerces.

What a mess.

-- Scott