Most people seem to be in agreement that velocity templates are at least an order of magnitude faster that jsp pages, which to me seems a bit...odd. So I was wondering if anyone has good (small) examples of this being the case. Webwork examples don't count as good examples because they involve a lot more than just jsp vs velocity, and might well be due to differences in webwork's velocity stuff vs webwork's jsp taglib.
So, can anyone take up the challenge, and prove to me that a velocity page that prints out some bean properties is faster than a jsp page which does the exact same thing? Maybe a very basic sample app that anyone can run to see for themselves?
Well, we have built our entire portal product on WebWork/Velocity, and although I don't have the same in JSP I'm rather convinced that the performance we get is to a large extent due to our use of Velocity. Here's a sample page:
http://www.konj.se/index.html
This page assembles a whole lot of dynamic data (ALL data you see is taken from an object model) and uses Velocity to render it. Typically such pages render below 100ms, and as you can see it's a whole lot more complex than the MonthList.jsp page which takes forever to render in JSP.
Not sure if this helps you, but I can tell you that at least I am very happy with the decision we made to use Velocity.
regards, Rickard
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
