Package org.niggle.templates

The base Niggle API's that abstract away your web app's interaction with page templates.

See:
Description

Interface Summary

Page	An abstract encapsulation of a page template.
PageFactory	An interface for an object that vends Page instances

Class Summary

LocaleUtil	An abstract base class for objects that wrap another object for presentation purposes.
ResourceBundleWrapper	An object specifically designed to "wrap" a Resource bundle containing externalized strings for a template engine that uses the get() hook, like WebMacro or Velocity

Package org.niggle.templates Description

The base Niggle API's that abstract away your web app's interaction with page templates. The construct that will be of most interest to the application programmer is the Page interface. Page is an interface that encapsulates the idea of an HTML page template in which you can embed dynamic data. In particular, via the expose methods, one can drop an arbitrarily complex data structure onto the page, consisting of hash, list, and scalar variables. Note that an Oreo data record is converted into a hash-type variable.

The design goal of these classes was that it would be possible to wrap up various page template solutions in this API. As of this writing, there are 2 concrete implementations, one that leverages the Freemarker template engine and another that uses WebMacro.. The Freemarker-based implementation is the default and has been subject to more testing than the one based on WebMacro.