Show of hands, tomcat versus jetty for idp v3?

[Cantor, Scott]

On 9/2/15, 7:12 PM, "users on behalf of Paul B. Henson" <users-bounces at shibboleth.net on behalf of henson at cpp.edu> wrote:



>We are finally going to start prototyping idp v3, and I was curious how many
>people are using tomcat 8 compared to those using jetty? I understand that
>jetty is the developer recommendation and primary development platform,
>however tomcat 8 is listed as officially supported.

The biggest argument I had against Tomcat is something we solved. Initially it was taking minutes to start up, and that turned out to be caused by the implementation of annotation scanning that doesn't work well if you leave the warfile packed. Jetty chooses to just kind of fall over when you don't let it unpack some things, but is clearer that it's a problem, vs. just not running well.

I'm a major anti-unpack person, so that bugged me, but Jetty more or less requires almost a full unpack anyway, so they're roughly on par on that.

With that mystery solved, I don't have any major issues with Tomcat that don't appear to be a problem with Jetty, like an absolutely terrible regression track record, lack of testing of patches, and completely clueless TLS configuration machinery

In short, I've hated Tomcat for a decade, and Jetty seems to be catching up with its latest release, so it's all good.

But for full disclosure, we don't have any continuous integration testing on Tomcat right now (or Jetty 9.3, which is why that was such a shock). It's on the list.

-- Scott