This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Thank you bear for the information. We can say jsp is a template language for template's a html page by replacing text response which is not a 100% define the word template. But velocity far more than it and you can template the html page it self by making separate areas for separate components. I mean more like tiles know.
The second fact is, it says Velocity is twiceas fast as JSP. Is the main reason for that is the jsp translation and compilation process? But jsp claims compilation into a Servlet for speed and efficiency reasons? Really whats the advantage here for bind the jsp in to a servlet container instead of just parse it and run as velocity.
I have read that,
The point being that this whole process of edit->transform->compile->load->run is really unnecessary and in particular, a bad design. On the other hand, Velocity will simply load templates, parse them a single time and then store an Abstract Syntax Tree (AST) representation of the template in memory which can then be re-used over and over again. The process is simply edit->parse->run.
The benefit is that working with Velocity templates ends up being much faster and it also removes the requirement of having a javac compiler and temporary scratch directory hanging around. In Velocity, when the template changes, the existing cached template is simply replaced with a freshly parsed version. The other important thing is that the actual template data can be stored anywhere, including a database or remote URI. By using configurable template loaders, it is possible to create template loaders that can do anything that you want.