Larry Isaacs wrote:
> A couple of comments:
>
> I would like to see a goal added like the following:
>
> X. With respect to JSP 1.1 issues, insure that Jasper in Tomcat 3.3
> remains compatible with Jasper in Tomcat 4.x.
>
Larry, are you thinking of "compatibility" from the functional viewpoint (i.e.
every JSP page that works in 3.x works the same in 4.x) or from a code sharing
viewpoint?
The former is something I would definitely favor -- backwards compatibility in
Tomcat 4.x is mandated by the specs, and having people actively concerned about
cross-checking is a useful mechanism to ensure it.
The latter, on the other hand, would be pretty difficult to achieve, because
Jasper in 4.x needs to be free to use Java2 classes where appropriate. I'm also
interested in looking at some more radical changes in Jasper that improve the
performance of the code that is generated.
>
> and under Release criteria something like:
>
> X. Port all appropriate JSP 1.1 related changes from Tomcat 4.x Jasper
> to Tomcat 3.3 Jasper. This includes all JSP 1.1 related bug fixes and
> all issues that would affect upgrading from JSP 1.1 to 1.2 should also
> be included. Other issues, such as name munging changes, may be included
> if deemed appropriate (with Vote if necessary).
>
> I also think it would be good idea to require Jasper's JspServlet still
> function properly if used in Tomcat 3.3, even though Tomcat 3.3 now uses
> an interceptor to manage JSP compilation. (Jasper is still used for
> translation to servlet source, but the interceptor controls the
> rest).
>
Makes sense.
>
> Cheers,
> Larry
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
