This is one of the main files of configuration of template.
In it is possible to configure which file go to be generated for each technology. Also where they go to be generated. For detailing, it it is the representation in XML of the class org.j2eespider.ide.data.domain.TemplateFile. Then it possess elements for all the attributes of this class.

In this tree we can see an attribute key of element <entry> that it defines the name of the configuration (that is directly on the technologies of the project) and other elements that define which files go to be generated.
For the CONFIG.LAYOUT a list of templateFile exists. Each templateFile generally has one path for the file of template (file of velocity or static file) and one path for where it goes to be generated the file.
The pathTemplateFile can still be an archive or a folder.
In case that it is folder, will be copied all files that do not finish with .vm (archives it velocity). For bigger flexibility and security, archives of velocity only can be generated individually, and not in groups.

The image above is one another vision of templateFiles.xml. Now in form of grid.
It is possible to visualize diverse configurations, as CONFIG.LAYOUT, CONFIG.LAYOUT.SPIDER1, CONFIG.LAYOUT.SPIDER2, and others...
In CONFIG.LAYOUT they are common rules to all layouts. In CONFIG.LAYOUT.SPIDER1 they are rules only of the layout spider1.
It continues thus...
Then the definitions on what it goes to be generated are hierarchic.
An important detail is that variables(as keys of the archive of resource) they can be used for customize path of the destination archive (click to see more details here on the variable).