tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Larry Isaacs <>
Subject RE: Outstanding bugs before 3.2 final?
Date Thu, 21 Sep 2000 11:13:01 GMT
Hi Sam,

I cleaned up some error handling last night and committed the changes this morning after some
further testing.  The change includes removing the stack traces from the default exception
handling.  I agree with Costin and others that this reveals more information than is

Is it possible to include these changes in beta-5?

The main spec issue that I'm aware of is that getServletPath(), getPathInfo(), and getPathTranslated()
still return encoded strings instead of decoded per the Servlet 2.2 spec errata.

It's not good for Tomcat 3.2 to not be in compliance, but would this be okay defer until Tomcat
3.3?  This issue hasn't had much impact in the work I do, so I have't formed a strong opinion
on this.


-----Original Message-----
Sent: 9/20/00 6:56 PM
Subject: RE: Outstanding bugs before 3.2 final?

Alex Chaffee wrote:
> > Please mark ( or send to the list)  all "MUST BE FIXED"
> bugs ( i.e. if not
> > fixed you'll -1 the release ).
> As far as I'm concerned, there are no such bugs.  "Release for the
> sake of release" is my motto.  Just get it to pass Watchdog and ship.

Nacho wrote:
> Agree!! 3.2 now is far better than 3.1 final, and 3.3 is becoming to
> be wayyyy better than 3.2, IMHO, is time for 3.2 !!! we all are tired
> of 3.1 issues, i think.

OK, I just submitted a build for beta 5.  I'll post it [ and announce it
this time, Hans! :-)] and put it up for a vote.

Once 3.2 is final, I plan to immediately post a 3.3 beta.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message