Tomcat 5.5 [PSARC/2008/065 FastTrack timeout 02/06/2008]

[James Carlson]

Joseph Kowalski writes:
> Update to Apache Tomcat 4.1 which is still being sporadically supported
> for security problems or to community fully supported version 5.5 (which
> is now in Nevada) would require users to recompile their application and
> possibly deal with several other incompatibilities with custom Realms,
> Valves or deprecated Apache Tomcat connector. Therefore the update isn't
> possible.

I see that 4.0->4.1 amounts to effectively a major version change, as
it doesn't provide application compatibility.

Is this also the upstream source plan for the future?  In other words,
should we expect that 5.6 will be incompatible with 5.5 in a similar
way, or is the 4.0->4.1 event an unexpected problem?

I ask because the "tomcat55" path name seems odd to me.  I would have
expected "tomcat5" here ... and dealing with a path that changes again
in the future would probably be annoying.

> Lists only newly defined paths from PSARC/2002/0096

How do users select which one they want to run?

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677