Show of hands, tomcat versus jetty for idp v3?

[Paul B. Henson]

> From: Cantor, Scott
> Sent: Wednesday, September 02, 2015 4:35 PM
> 
> 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.

Ah, yes, we've had a few annotation issues in the past. I vaguely recall having to configure tomcat not to do it on a couple of jars that were problematic.

> 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.

I don't think I have a strong opinion on unpack versus not unpack, other than it seems kind of silly to bundle everything together into a big war file and then just rip it all back out again :). And it's insanely annoying when a webapp which doesn't have an externalized configuration file needs a minor tweak and you have to completely rebuild and redeploy the war <sigh>.

> 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.

There's only so much hate a body can have ;). Thanks for the update, I feel a little better about sticking with tomcat for staffing efficiency purposes now. 

--
Paul B. Henson  |  (909) 979-6361  |  http://www.cpp.edu/~henson/
Operating Systems and Network Analyst  |  henson at cpp.edu
California State Polytechnic University  |  Pomona CA 91768