tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30980] - Separating Static and Dynamic content in Jasper generated Java class to avoid compilation
Date Thu, 02 Sep 2004 05:28:07 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30980>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30980

Separating Static and Dynamic content in Jasper generated Java class to avoid compilation





------- Additional Comments From callbabusats@yahoo.co.in  2004-09-02 05:28 -------
jspc is not invoked in deployment mode.
Hence this feature will add overhead in normal jsp access from class files.

But,In development mode, jspc is invoked for every change in static html.
There are additional requirements
-Intermediate file
-Properties file
per JSP file, it may be possible to combine them.

A switch like jspc -static_split may follow this procedure.

When there are frequent changes to jsp file, this process will reduce response time.

When jsp files are accessed frequently without changes this will increase
response time.

+Avoids jspc
+Avoids javac

-Requires 1 or 2 files per jsp
-class files do not have embedded strings, hence there is a runtime performance hit.

But the algorithms of diffing,querying do not put any oiverhead.

Will it be worthwile to develop a module for -static_split? I belive this will
aid developers, as it removes compilations.

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


Mime
View raw message