In Adelia Studio V14.4.0 and later versions it is strongly recommended to use the multi-platform code editor Visual Studio Code together with an extension that is supplied "APE Template Editing" and which automatically centralizes all the programming environment functions: code editor, APE instance and REST client.
This environment should include at least:
- a text editor to edit an .ftlx file.
A simple text editor may suffice (Notepad, Notepad++) if it is able to save a file in UTF-8.
However, an editor with syntax coloring helps with programming. This editor must be FreeMarker and/or XSL-FO compatible.In the Adelia Studio product, we offer an extension that is compatible with the Visual Studio Code multi-platform code editor. This "APE Template Editing" extension makes it easier to edit the APE template by providing input help such as syntax coloring, auto-completion, contextual help, etc.
Other more general editors are also available.
Click below for more information:
- an APE instance (if you are not using the Visual Studio Code extension - not recommended).
So that the development cycle is short, we recommend using the MergeTransformMicroService application (even if your templates have to be used via the VaToolBx toolbox).
To do this, you need to specify a particular freemarker.properties file when starting the application, in which you will define a "file system"-type template loader to your template creation directory.
For example: com.hardis.adelia.mergedocengine.freemarker.conf.FileTemplateLoader(java.io.File ("c:/TemplateWorkspace")), - a REST client to test the execution of your templates (if you are not using the Visual Studio Code extension - not recommended). See "REST client" section in "Use via RESTful Web services".
For data supply, either work with a production data sample or with simulated data.
Click here for more details >>