Perhaps bacause 3.2.3 is the last version using Jetty.

Upgrading from 3.2.3 means a new web container :-(

We still use 3.2.3 because with Jetty we are able to dynamically mount web contexts in the filesystem. I dont know if this is possible with tomcat but when i looked at it a long time ago, i could'nt find any other way of doing this than changing tomcats server.xml (which is not very dynamic)Perhaps i missed something, but the point is these kind of things could be the reason for the heavy use of 3.2.3.

terp

Jetty Performance: http://www.webperformanceinc.com/library/ServletReport/

-Andy