deploying the current Shib v3 snapshot on Tomcat

[Cantor, Scott]

On 9/3/14, 7:27 PM, "Michael Stroucken" <mxs at cmu.edu> wrote:

>>Because the default config *doesn't* lead to that exception. But in
>> general there is no way to know if it will or not. If you carry over a
>> container that was endorsing Xeces/Xalan, then it would throw. If not,
>>it
>> won't.
>Default configuration using Jetty? I had not made any modifications to
>the configuration as it came from the download, and it was installed as
>a new webapp.

No, default period, has nothing to do with Jetty. Unless Tom's change
caused Xerces to show up in the distribution all of the sudden, which I
guess is what he was saying just now. That's not going to be there later.
The missing logging jars should also be fixed now.

>I am not familiar with the "endorsing" concept yet, I don't recall
>having ever made a choice about it, but I'll look more into that.

I assumed you must have installed into a container that was running V2
before, which requires Xerces, because I didn't know something had changed.

Anyway, as far as as alpha-2, out of the box uses Sun's parser and there
was no issue. There will be an issue for upgrades unless people un-endorse.

There is no way to apriori get this right. We stop requiring a specific
parser and we're then forced to leave the eventual configuration of the
parser in the hands of the deployer. Can't win. It's just bad design from
Sun/Oracle.

-- Scott