idp 5.11 with Jetty 12, duo fail

[Cantor, Scott]

> I do see you went with ee10 instead of ee9, given jetty 11 was ee9 I assumed that was a
> safer bet than ee10, but maybe I was wrong…

I used an old module file I created back when I was first playing with 12, I don't know if there's a requirement to do it or not. But the IdP was fixed to support both APIs because Spring required it so I didn't see much reason not to use the latest one.

> How come you didn't get this error with about the same config? Does your jetty tmp
> directory not have both a webapp and webinf directory with separate copies of the
> jars?

The testbed is not "normal", it mounts the idp-war folder directly via relative path as the webapp to deploy so there's no war file.

It looks like they treated your question as a bug. I assumed we were just using improper combinations of settings or something. The whole reason we always set extractWAR to false was because unpacked wars lead to corrupted behavior because of jars not being cleaned up, that's why Tomcat is so broken all these years.

I don't recall when we found the copyInf option or why we did that, it could have been for efficiency in scanning, or it may have been required at some point.

Anyway, looks like they have a bug, which doesn't surprise me, that's why I caveated it. If the only way for it to work is to set extract to true and copy to false I guess that works, but I would be concerned long term for the same reason I don't trust Tomcat.

-- Scott