I would like to receive feedback from people who used Velocity templates to generate web pages. Isn't Velocity aging and being replaced by new versions of JSP? Or maybe this is still great language for presentation layer in web application and better than JSP. I am not sure if it is worth studying since it's pretty old.. Maybe it's quite enough plain JSP and servlets. I know IntelliJ IDEA uses it to generate source code, but I am interested only in web applications now.
So my question is : is it worth spend time and learn Velocity?
There's so many techs out there that IMO it's not worth investing time and energy in any unless there's a specific business need NOW. Not only can't you know whether you'll ever use it but the environment is also changing fast enough that any study you do now may be outdated by the time you get to use the product for real.
Personally I use JSP (with JSTL) or XSLT/XML for output, I see no need for yet another output technology and that includes Struts taglibs.
Age of a technology in itself doesn't mean it's bad, in fact I much rather use mature technology as it's more likely to be stable and relatively free of at least major bugs. I've had to work on one major project with a product that was under hot development and it wasn't pretty. Having to rewrite half your codebase every other week because the next beta invalidates it all isn't what you want when you're under a deadline and the money is pouring out the floodgates.
For pure web pages, I'd go with JSP. However, I'm about to embark on a project where I need to do non-web text substitution not neccessarily in a J2EE container. For that, I'm planning to use Velocity just because I'd expect that Velocity might run faster in a high-traffic environment and I don't need HTML headers, a servlet-style framework, or the extra syntactic sugar that makes JSP such a nice fit for producing web pages and XML files.
So I think Velocity's not likely to die yet. In fact, I'd be tempted to replace the custom macro processor in my EJBWizard app with Velocity if I thought it could handle some of my internal wierdnesses. I just prefer JSPs where JSPs are strong and Velocity where Velocity is strong.
Sources may include data from the Fakebook Research Foundation with support from Gargle University
hi, check this link http://jakarta.apache.org/velocity/casestudy1.html it is a case study comparing jsp with velocity. But i still agree with Jeroen it is better to use an existing technology, just think of the time and effort spent to learn and implement a new technology .Furthermore there will be a lot of developers who use the existing and mature technology so u can expect a lot of people to help u if u are stuck at some point in ur project. regards, karthik
JavaRanch is a community of people from all over the world, many of who are not native English speakers. While using abbreviations like "u" instead of spelling out "you" is convenient when text messaging your friends on a cell phone or in a chat room, it presents an extra challenge to those that are already struggling with English. I would like to ask for your help in making the content of JavaRanch a little easier to read for everybody that visits here by not abbreviating such words.