Container and Tomcat testing

[Cantor, Scott]

Jetty situation:

We have our Jetty 9 plugin to fix cert handling. I think the technically 
minimum version for servlet 3.0 is Jetty 8. I don't think we should bother 
with that for support at this point, it was kind of a "runt" release 
anyway, so I suggest we stick to 9+



I tested some other possible options to avoid the cert plugin, but while 
they have some weird options in the connector like a "TrustAll" property, 
they don't really work right. Nor does it appear you can override the 
TrustManager class directly, so I don't think we have a simpler 
alternative there.

Tomcat situation:

I've spent most of today working with Tomcat 8. After working through 
bugs, I got far enough to test the cert handling, and the direct override 
of the TrustManager class appears to work. I created a project last night 
with that code in it in our own namespace and added it to Jenkins. The 
only reason not to put that one class into java-support is that we'd have 
to have people copy java-support out into tomcat/lib, and we don't want 
version conflicts after IdP upgrades.

There are a few other issues with Tomcat, at least with 8, and at least 
one thing (JSTL) we'll have to cover tomorrow in the call and discuss. 
Also having an issue with startup time, will do some more research on 
that. Seems connected to annotation scanning.

I noticed a slightly annoying thing, using JSP templates causes ERROR 
logging from Velocity because it can't find the equivalent view. Not much 
we can do about it, we could install some log filters to block those I 
guess.

-- Scott