Hello all,

I have changed our build process to precompile JSPF pages along with JSP pages. 
This solves known bug 628555 (ServletException/JspException File not found 
/usr/share/tomcat6/work/Catalina/ ... /jsp/WEB_002dINF/ ...) and also speeds up 
application responses after startup (no server pages compilation needs to be 
done now - you may noticed some links were slower than others when clicking for 
the first time).

I have upgraded the jasper2-compiler library in the ivy.xml to version 5.5 (we 
use this version in RPMs), created a internal class that sets file extensions 
for Jasper2 properly, changed the jasper2 taskdef in our build-taskdefs.xml and 
fixed a LOG4J warning in the precompilation build step. By precompiling those 
pages I have found three minor problems in JSPF files: one was no longer in use 
and two was missing a jsp tag definition. I have fixed that. Our package will 
be slightly bigger because instead 446 compiled pages (class files) we have 
561. That's nothing.

If you run into problems let me know.

commit 3fd124cb5b3c61319ed94c3cacd37a54b8175729
Author: Lukas Zapletal <lzap+...@redhat.com>
Date:   Wed Sep 29 17:33:51 2010 +0200

    jspf pages are now precompiled too

commit eee9e5fba8c7562e8c8cb978f27ac38883079a0e
Author: Lukas Zapletal <lzap+...@redhat.com>
Date:   Fri Sep 24 16:56:23 2010 +0200

    deleted jpsf that was no longer in use

Sent to user's list by mistake. Please respond here.

Later,

 Lukas Zapletal | E32E400A
 RHN Satellite Engineering
 Red Hat Czech s.r.o. Brno

_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel

Reply via email to