2.4.0 / September 11, 2011
ztemplates runs in any standard java web application container like Apache Tomcat.
ztemplates extensively uses annotations and so requires almost no configuration. It is centered on urls and allows the definition of url-variables and url-references so the programmer can extract more information from the url than is usually possible.
The active part of a ztemplates application is located in callbacks. The callbacks and the sequence in which they are called are defined by the url. The programmer can define before and after callbacks for all actions, url-variables and url-references. They are called in the order in which the corresponding url-variable and url-reference are defined in the url.
The web-page rendering is done with standard technology, like JSP, Apache Velocity or FreeMarker. ztemplates chooses the correct rendering technology and template from the annotation the programmer attaches to a plain old java object.
ztemplates integrates with maven and is available from the maven central repository.
ztemplates also integrates with Spring and exposes its services as spring beans.
The rendering part and the actions are completely independent of each other.
- JSP, Apache Velocity and FreeMarker compatible. This can be extended by implementing a simple interface.
- Support for selfcontained components that can be included by dropping a jar file into WEB-INF/lib.
- state-free. ztemplates does not keep server-side state.
- technology agnostic urls. There are no constraints on the urls by the framework.
- invisible to the web-client. ztemplates is not visible to the web client, so it could be replaced by other technologies without breaking your application.
- extensible through services. ztemplates extensively uses interfaces and annotations, making it possible to replace every part of ztemplates with a custom implementation.
- security with annotations. ztemplates provides support for security by annotations.
- Spring support is available for action pojos.