This is a module for Play! Framework 1 applications which replaces the default groovy template implementation with GT-Engine which is faster and uses less memory.
GT-Engine is also used in the Play 2.0 module that enables legacy support for groovy templates.
See below how to download the plugin from my site.
- Version 1.10 - 29 Oct 2018
- Upgrade to Play 1.5.1
- Version 1.9.5 - 09 Aug 2018
- Upgrade to Play 1.5.x which is Java 9 compatible
- Version 1.9.4 - 27 Jun 2017
- Code cleanup
- Version 1.9.3 - 14 Jun 2017
- Performance improvements
- upgrade to gt-engine 1.0
- Version 1.9.2 - 9 Jan 2017
- Support for the latest Play 1.4.x that adds Java 8 parameter support
- Version 1.9.1 - 4 Jan 2017
- Includes some fixes made to gt-engine, e.g. support for BigDecimals in #{if}, #{extends} has access to template's variables
- Version 1.9 - 3 Jan 2017
- Added support for empty Map in #{if}
- Version 1.8 - 12. April 2013
- Fixed missing-args bug when invoking some Groovy methods. If groovy method name was equal to a JavaExtension-method-name, the args to the methodcall could be null.
- Version 1.7 - 8. May 2012
- Fixed issue #19 - Improved parsing when using {} inside ${}
- Version 1.6 - 8. April 2012
- Fixes issue #18 - Listing enums with #{list} now works
- Version 1.5 - 19. mar 2012
- Fixes issue #17 - No more name-clash-problem with static methods and JavaExtensions
- Version 1.4 - 4. mar 2012
- Fixed issue #13 - More intelligent when finding end-of-tag '}'
- Fixed issue #14 - GroovyTemplate.ExecutableTemplate.getProperty
- Version 1.3 - 27. feb 2012
- Improved error reporting
- Version 1.2 - 19. feb 2012
- Fixed issue related to calling method on java object with name-collision with JavaExtension-name
- Version 1.1 - 14. feb 2012
- Fixed various bugs related to #{set/} and #{get/}
- Version 1.0 - 12. feb 2012
One way of including the module is by using the dependencies.yml file. Remember to call "play dependencies" before "play run" the first time.
Use dependencies.yml like this to download the plugin from my site:
require:
- play
- play-codeborne -> fastergt 1.9
repositories:
- codeborne:
type: http
artifact: https://repo.codeborne.com/play-[module]/[module]-[revision].zip
contains:
- play-codeborne -> *
Download it from github (or git clone it), then add dependency to it like this:
require:
- play
- faster-groovy-templates -> faster-groovy-templates
repositories:
- My modules:
type: local
artifact: ${application.path}/relativePathToWhereYouDownloadedIt/[module]
contains:
- faster-groovy-templates
Or you can add it do the application.conf file like this:
module.faster-groovy-templates=../relativePathToWhereYouDownloadedIt/
- Almost 100% compatible with old Play Groovy template implementation (See note below for more info)
- Run faster
- Compiles faster
- Can write generated source to disk so you can step-debug it
- Uses less memory
- Supports old FastTag
- Supports new GTFastTag which is optimized for inserting rendered tag-body-content (without copying)
If you use program-flow-fragments inside groovy code snipits you have to modify it like this:
You can no longer use partial-program-flow-code like this:
%{ if( expression) { }%
or
%{ myList.foreach() { }%
Instead you have to use:
#{if expression}
or
#{list myList}
If you find issues, please report them here: https://github.com/mbknor/faster-groovy-templates/issues
Issues:
Unnamed closing tags do not work, instead of #{if xxx}#{/} write #{if xxx}#{/if}
JavaExtension methods with varargs, but without any varargs passed cannot be called
Strings cannot be iterated directly using #{list s}, use #{list s.toCharArray()}
There is no function ${get('var')} that returns the value set using #{set var: ''}
JavaExtensions don't work inside of groovy lambdas
Note if you also use the CRUD-module: The original CRUD template files uses a lot of partial-groovy-code-snipits. Since this is not supported in gt-engine, faster-groovy-templates includes its own version of these template files - with fixed syntax. You don't have to do anything special. These files are used automatically.