+1, I think most things will be easier now in jasper34 space, JspServlet
was one of the scariest things but it's starting to look better.
BTW, did anyone tested the per-session encoding stuff ? Can we keep it on
by default ( given that all known browsers will post in the same encoding
the form is receiven into ) ? I'll try to write a small doc on how charset
works later on, when I get more time - but I would like to know this area
is ok, it was one of the biggest things on my list for 3.3.
Costin
On Sun, 17 Jun 2001, Larry Isaacs wrote:
> Hi,
>
> Continuing to adapt the Tomcat 3.3 schedule to available time and needs,
> I propose the following changes to the current RELEASE-PLAN-3.3:
>
> Add a Milestone 4:
>
> Code Freeze/Tag Date: June 20, 2001
> Release Manager: Larry Isaacs
>
> This release contains a switch to using jakarta-tomcat-connectors
> for some utility classes. It also uses jakarta-tomcat-jasper
> for building jasper34, which will be enabled as the default
> JSP handler. The internal "jasper33" will be enabled as the
> default JSP handler for future releases of Tomcat 3.3.
>
> Known issues in order of priority:
> 1. Jasper34 needs to be stable.
> 2. Watchdog and internal test need to be passing all tests.
> 3. Build documentation need to be updated to document
> new dependencies on jakarta-tomcat-connectors and
> jakarta-tomcat-jasper.
>
>
> Change the Beta 1 Freeze Date to July 11.
>
> Change the Beta 2 Freeze Date to July 18.
>
> Change the Final Release August 1.
>
> Cheers,
> Larry
>
