> I'm about to start a new project, and we have decided > to use WebWork. I'd like to hear what kind of view > technology the WebWork users/developers recommend.
Good choice! I have used Velocity, but support for JSP is a way above from what WebWork gives to Velocity users. I have since switched to maverick as it is more democratic when it comes to view layer support. > I'm hesitating between Velocity and JSP. I think that the best bet is to use JSP, but you might also be interested in Velocity tags-libs: http://jakarta.apache.org/velocity/veltag.html. > I prefer Velocity over JSP because it's quicker to use > for development (no need to recompile as with JSP), Me too. I also like to use whatever fits better in particular place. I currently develop with JSP (SiteMesh) with taglibs, Velocity, Freemarker, XMLT/Domify and DVSL. It's great to have support to these whenever thay comes handy. > But as far as I understand, I won't be able to use > the WebWork JSP taglib from Velocity, and that rules > out the EL too. (Correct me if I'm wrong). You are mostly write, but I solved this problem by writing Velocity tool that gives you EL support (not very hard). And you can use taglibs if you like - with or without velocity. See veltags and for e.g. SiteMesh. > Basically I want to use Velocity + WebWork tags + EL > (but not JSP). Is it possible? Yes, but it takes some more effort from your side - not too hard. > Bonus question: Has anybody tried to use Jelly with WebWork > to render views? I have not. Regards Aapo <b/>ungle Laakkonen ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
