Patrick Lightbody wrote:
Another thing that could be an idea is to use Velocity for the templates. I measured the raw overhead of doing an RD.include() on an empty Velocity template and an empty JSP. The overhead was way higher for a JSP, so in any include-intensive situation (e.g. tag templates) Velocity is a better choice.I believe that rewriting it to work for Lists would be just fine. The main thing it is doing is essentially _skipping_ all the EL stuff, which I believe is "OK" since templates are only usually edited once.
And same as above applies: they're only usually edited once so what it's implemented with isn't that important.
Another good thing about using Velocity instead of JSP is that the performance is more consistant since it's not reliant on the JSP engine quality which, in some cases, is not what it should/could be (Tomcat/Jetty for example).
/Rickard
-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
