Aslak Hellesøy wrote:
Not with the same transparent syntax, since the Velocity templates use the Velocity language. I.e. if you'd want to use the WW EL then you'd have to delegate to WW explicitly, e.g. $stack.findValue("foo").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. I'm hesitating between Velocity and JSP.I prefer Velocity over JSP because it's quicker to use for development (no need to recompile as with JSP), and it has a more elegant syntax. -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). Basically I want to use Velocity + WebWork tags + EL (but not JSP). Is it possible?
I personally use WW and Velocity almost exclusively, for three reasons:
1) Speeeed. Velocity is much faster, especially in a case like ours where we do perhaps 10-20 include's for each page rendering. You simply can't do that with JSP and have decent performance.
2) Syntax. To me the Velocity syntax is cleaner, although not as powerful as JSP. Definitely good enough though.
3) Not having to put templates in files. Some of our templates are just strings in our database, and some of the templates come from resource bundles, etc. You just can't do that in JSP.
The only thing I use JSP for right now are pages that need the form tags, and I intend to migrate those to Velocity too when the tags are so generic that they can be used regardless of view. Shouldn't be that hard to accomplish.
/Rickard
-------------------------------------------------------
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
