Part of it's comfort as well. I *know* 4.1.x quite well. I've been using it for a while now, and been very satisified with it. And just because 5.x becomes the new 'production standard', doesn't automagically make all 4.1.x installs somehow break in odd and mysterious ways.
If someone could *confirm* this is a 'known issue affecting 1.1% of installs' or some such... then for sure, I can try the move to 5.x today. What is most frustrating is that this was working last week, and ZERO changes have been made to config files. I don't think our box has even been rebooted in more than a month. The last config file change (aside from my mod to conf/web.xml today) was to server.xml on Dec 15, to remove some dead Contexts. It ran for several days after that, just fine, recognizing changes as I was developing all last week. I've even rolled that change back, and no dice. > -----Original Message----- > From: Remy Maucherat [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 23, 2003 1:31 PM > To: Tomcat Users List > Subject: Re: JSP not reloading > > > Mike Curwen wrote: > >>3. Did you try upgrading to 5.0.16? *duck* > > > > no, we're not wanting to use 5.0 until (probably) 5.1. There's > > nothing we need from the new servlet spec. > > You're free to do what you want, of course, but I'd like to point out > 5.0 should have been named 4.2. The major revision number > switch is only > because the specs were upgraded. > > If you were following tomcat-dev, you would have seen that there has > been no intention to start a 5.1 branch so far, unlike what > has occurred > in the past (4.1 was branched from 4.0.0 Final, and 5.0 was branched > from 4.1.7 Beta). So there may not be any major new release > until Tomcat > 6.0. We'll see :) > The future of the 4.1.x branch depends on the stability of the more > refined 5.0 branch, and from the reports from 5.0.16 testing, > it looks > like it may not live very long. > > -- > xxxxxxxxxxxxxxxxxxxxxxxxxxxxx > R�my Maucherat > Senior Developer & Consultant > JBoss Group (Europe) S�RL > xxxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
