Since moving to web application frameworks (jakarta turbine and ww2) I've exclusively used velocity. I find velocity's syntax to be simple, clean, and sufficently powerful for constructing views. I mean, when you get down to it, a view is simply html (in most cases), and velocity does it nicely. Custom macros and the #parse() marco allow me to create modular .vm files that can be reused many many times.<snip>
Ditto that. We've built our CMS/Portal product to use WW/Velocity exclusively, and we're VERY happy with that. The major pro's we've seen are:
1) Clean syntax
2) Great performance
3) Templates does not have to be in files (JSP files do)
All in all, much recommended.
/Rickard
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
