API / Apache Velocity Interview questions
What are the main features of Apache Velocity?
A few characteristics come up repeatedly when Velocity is discussed against other Java templating options.
- Clean separation of concerns — templates hold presentation, Java code holds logic and data.
- Simple, minimal syntax — references, directives, and comments cover most needs without a steep learning curve.
- Reusable macros — Velocimacros (
#macro) let you define reusable snippets like a function. - Pluggable resource loading — templates can load from the file system, classpath, or a custom source.
- Framework independence — usable in servlets, standalone apps, Struts, Turbine, or code generators like Maven archetypes.
- Fast compilation and caching — parsed templates are cached as an AST so repeated renders skip re-parsing.
None of these require a servlet container, which is why Velocity has historically been popular for generating emails and config files outside a web request too.
Which Velocity feature lets you define a reusable, function-like template snippet?
Why can Velocity generate emails or config files outside a web request?
More Related questions...
