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 Summary: Separating Static and Dynamic content in Jasper generated Java class to avoid compilation Product: Tomcat 5 Version: 5.5.0 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: Other Component: Jasper AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] A JSP file is made to Servlet with static content emitted as out.println directly <html><body>Hello</body></html> as out.println("<html><body>Hello</body></html>"); This means any change to static content, requires jspc and javac i.e 2 levels of compilation. Alternative A jsp file is made to Servlet file with static content referenced by a variable from a file JSP File1.properties StaticContent1=<html><body>Hello</body></html> out.println(resourceBundle.getKey("StaticContent1")); // This is pseudo code When the jsp file changes to <html><body>Hello JSP World</body></html> Only JSP File1.properties is modified as StaticContent1=<html><body>Hello JSP World</body></html> There is no recompilation - The resourcebundle is assumed to fetch right value JSP can manage properties file, rather than developer doing it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
