Parallel question:
How many think that the public messaging should be that more along the
lines of Tomcat 5 is now at least as stable/mature as Tomcat 4.1.30
and that folk should upgrade to it?
Having asked, I still believe a 4.1.31 for such an issue as that brought
up here would be
Hi,
It's unlikely you'll see a 4.1.x release for any one feature, unless
it's a critical security fix. 4.1.x will have bundle releases with
several features, less frequency. We've been giving the message for a
while now that 5.x is the way to go, not least because less resources
(including
Glad to hear it. Perhaps I'm dense, but this stance is not readily
apparent from the Tomcat web page.
Contrast:
*Tomcat 4.0.x*. Tomcat 4.0.6 is the old production quality release...
with
*Tomcat 4.1.x*. Tomcat 4.1 is a refactoring of Tomcat 4.0.x, and
contains significant
So what I've brought up is not a critical security fix, but instead a
critical functionality fix, with a workaround that is quite annoying for
end users.
How does that rate?
Yes, Tomcat 5.x is the way to go, but for instance on support packs
for NetWare we are not at liberty to make such a big
Hi,
So what I've brought up is not a critical security fix, but instead a
critical functionality fix, with a workaround that is quite annoying
for
end users.
How does that rate?
Below a critical security fix. Personally, I wouldn't rate the
JNDIRealm as a critical piece of functionality
So what I've brought up is not a critical security fix, but instead a
critical functionality fix, with a workaround that is quite annoying
for
end users.
How does that rate?
Below a critical security fix. Personally, I wouldn't rate the
JNDIRealm as a critical piece of functionality either, but
