I'm a newbie to the front end. I will likely be designing a web application using Struts. I need to choose a method of page generation, but don't know quite what the various technologies are used for, and what their strengths are. So I'll put the question to you: Which is better, velocity or jsp? Does velocity solve the same problems as JSP in general, or does it correspond in function to JSTL? Aside from JsP and velocity, which other page-generation technologies do you like?
Learn the platform before you start to meddle in obscure addons like Struts and Velocity... I've read up on Struts, thought it overly complex (like most general purpose frameworks), like shooting a mosquito with an elephant gun for most applications. Haven't used Velocity, but it looks nice as an addon.
Struts is a bit over-bearing. Take a look at Spring (http://www.springframework.org) sometime. Velocity and JSP/JSTL are very similar except that Velocity uses uncompiled templates, while JSP compiles into servlets. I have used both and prefer JSP/JSTL. Both technologies kind of force you to do more object oriented design and planning up front... if you don't you may find yourself in some weird situations. JSP all by itself is best to start with... and it is flexible enough that you don't have to be an architect to get the full benefit out of it. Hope this helps.
- Chris Stehno, SCPJ
Joined: Apr 08, 2003
Thanks, folks, for the suggestions. They were helpful. I'll take Chris's hint and look at JSP first. It makes sense that JSP is a bit less leveraged, therefore less cantankerous to start off with.
subject: Which is better (and for what): JSP or velocity?