Definitions
The following define the contents of a JPlate Template:
Internally within ${ } the rules are similar to XML:
Please note: There can be any number of name/value pairs or none. A name may have an optional value.
The following are some stand alone directives:
${Foo/} ${Bar start end="12:00"/} ${zeta5 singularity="true" multiverse"=False"/}
${Foo} This is the contents of directive, Foo... ${/Foo} ${Bar start} This is the contents of directive, Bar... ${/Bar} ${GrandParent} Some data ${Parent first="Scot" last="Floess" I am so great ${Child nickname="Tabbi" female} My daughter ${Pet animal="Rabbit" name="Jack"/} ${/Child} No more data {$/Parent} ${Date today/} ${/GrandParent}
Please note: the template engine does no data organization
whatsoever. Data organization is up to implementations of
org.jplate.tmplate.parser.JPlateParserStrategyIfc
- and is
required to parse. The interface is an example of the Design Pattern
Strategy. Structuring the parser in this fashion keeps it simple as
well as allowing implementations to decide the correct "meaning" of the
JPlate data.