Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Developers List" <torque-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Subject: groovy support in generator & typed model in templates
To: torque-dev@db.apache.org
Message-ID: 
 <OF7906058E.9F07F359-ONC1257B62.00476EB5-C1257B62.00487619@seitenbau.net>
From: Thomas Fox <Thomas.Fox@seitenbau.net>
Date: Sun, 5 May 2013 15:11:25 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


The groovy support in the generator is now finished.
There are 2 supported groovy template types: groovy scripts and groovy
templates.
A script returns the result string as a return value.
A template returns the text of the template files, one can use dynamic
parts in it. See http://groovy.codehaus.org/Groovy+Templates for details.
Unfortunately, the eclipse groovy plugin only supports groovy scripts, so
I'd personally rather not use the template variant.

As an example I have changed the sql generation from velocity to groovy,
using the script variant and a typed model.
Please have a look and check whether this is better to edit/understand than
the velocity templates (in my opinion, due to the typed model and editor
support, yes).
Please use the eclipse groovy plugin for viewing the cripts as it provides
conciderable value (sytax highlighting, code completion...)
A small problem is the long startup time of the groovy script engine, ca. 1
sec on my machine, but this is needed only once per generation run.

Then the decision would be whether for the templates, we want to switch
back to velocity, switch over to groovy, or leave the current status (part
groovy, part velocity)

I'll be in holiday in two days for over a week, so there is no need to
hurry.

    Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org