Alright, so based on the feedback so far, the consensus seems to be:
webwork jsp UI tags are much slower than velocity equivalents. So the culprit seems to be the webwork UI tags, not jsp itself.
Well, it's the base JSP include overhead that is bad, really. Including a JSP has in my own benchmarks a 2ms overhead. For some applications, like our portal product as an example, that is just totally unacceptable. Velocity has a vastly lower overhead for includes, as boxed said practically no time at all.
/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
