deploying the current Shib v3 snapshot on Tomcat

Cantor, Scott cantor.2 at osu.edu
Wed Sep 3 12:06:50 EDT 2014


On 9/3/14, 5:24 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>Caveat : I don't really know what I'm doing ... but ... I've been
>using the testbed to test the consent flows, and after a little while
>I got tired of clicking, so I added Selenium to the testbed, and
>Selenium brings along Xerces/Xalan so our default configuration does
>not work, as described in this thread.

That may be true, but won't be true of the eventual distribution of the
software.

> So I added the following to the
>app ctx initializer, which adjusts idp.properties in-memory, not
>on-filesystem, as a workaround. It's wrong because ClassNotFound and
>IllegalArgument exceptions should be handled differently, but it
>"works".

Yes, it works easily enough when you're coding around a specific
configuration choice, I'm just saying that I don't *think* it's true that
if that class is found and loads, that means the JAXP calls will be
returning that parser implementation. But maybe that's not true. I've
never been clear on the JAXP override stuff because even after they
renamed the JDK classes to com.sun.*, you still couldn't override the JAXP
implementation without endorsement. But since I think they fixed that bug,
it's possible "Xerces in classpath -> Xerces is the JAXP impl" now.

-- Scott



More information about the dev mailing list