I think the answer is no -- you should recompile all JSPs. Would defo be the safest option anyway.

Eddie Ruvinsky wrote:

Resending this. Does anyone happen to know the answer
to this? Is this supported?

Thanks in advance,
Eddie

--- Eddie Ruvinsky <[EMAIL PROTECTED]> wrote:

In Tomcat 4.1.x, is the Jasper 2 runtime supposed to
be backwards compatible the Jasper 1 runtime (i.e.,
from Tomcat 4.0.x), so that existing precomiled JSPs
using the Jasper 1 compiler would work as-is with
Jasper 2 in Tomcat 4.1.x?

Thanks,
Eddie

--- Remy Maucherat <[EMAIL PROTECTED]> wrote:

A new test milestone of Tomcat 4.1 has just been
released. Please help test this upcoming Tomcat release for compliance
issues and other problems.

Downloads:


http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.13/

Significant changes over 4.1.12 include some
performance improvements as well as bugfixes.

The full list of changes is available in the

release

notes.


http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.13/RELEASE-NOTES

IMPORTANT NOTE: Security manager functionality is
broken in this milestone. This will be fixed in the next

milestone.

This milestone will not be proposed for official release, and should

be

used for testing purposes only.

Remy


__________________________________________________
Do you Yahoo!?
HotJobs - Search new jobs daily now
http://hotjobs.yahoo.com/

--
To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>






--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>

Reply via email to