Kai Moritz [Mon, 27 Feb 2017 17:47:26 +0000 (18:47 +0100)]
Ported app to Thymeleaf 3.0.x
* Proted the dialect to the new Thymeleaf-API
* Removed modified configuration of the default-template-resolver, because
it is not needed any more: Thymeleaf 3.0.x resolves its templates via
Spring's resource-chain by default.
Kai Moritz [Fri, 8 Jul 2016 16:34:55 +0000 (18:34 +0200)]
juplo:variables accepts expressions as arguments
juplo.variables now also accepts an expression as argument.
If the parameter can not be parsed as an expression, it is handeld as before
(i.e. parsed as JSON, if possible, tried to be reolved, if not). If the
expression evaluates to an empty string, the parameter is ignored.
Kai Moritz [Thu, 7 Jul 2016 11:42:56 +0000 (13:42 +0200)]
juplo:variables parses its parameter as JSON and can merge variable-defs
* If the parameter can be interpreted as valid JSON, juplo:variables uses
it directly as input.
* The parameter accepts special keywords, that controll, if variables, that
have been imported earlier, by a call to juplo:variables from an
ancestor-tag, will be merged or simply overwritten.
Kai Moritz [Sat, 18 Jun 2016 10:26:02 +0000 (12:26 +0200)]
Implemented juplo:variables, that imports variables from JSON-data
The processor interprets its argument as name of a thymeleaf-template and
parses the retrieved template as JSON-data. The root-element of the JSON-
data has to be an object. The variables, that are defined in this object,
are imported as node-local variables.