If operationName is set, the wizard works in batch mode and generates the files for that single operation without opening the UI. Since operations are not part of the model, all values the UI would ask for must be given as parameters, for example:

mvn tentackle-wizard:operation -DoperationName=SendInvoice -Dcomment="sends an invoice"

Best invoked from within the directory of the maven parent of the project.

The code a developer writes is only a fragment. It is woven into a harness: a freemarker template (provided via the harnesses filesets) that owns the boilerplate — it connects to the database, implements a DomainContextProvider so that on() and op() can be used, and defines the run() method the fragment is inserted into. The first line of a harness is a she-bang selecting the scripting language (for example #!groovy); it does not land in the generated script.

Since the fragment is inserted into the run() method, it cannot contain import statements itself. Instead, the fragment marks such lines with a leading ^-sign, for example ^import org.tentackle.misc.* in Groovy or ^require 'json' in Ruby. Every line starting with an ^-sign is removed from the fragment, stripped of the ^-sign, and provided to the harness via the imports model variable, which places it at the top level of the generated script.

The freemarker model provides four variables: content (the fragment), imports (the import statements extracted from the fragment), language (the language name) and harness (the harness filename).