QueryJ has built-in capabilities to perform actions (focused on generating code) based on the relational model it sees.

In particular, QueryJ 0.7 provides the following criteria:

1. Code to generate for each table of the model.
2. Code to generate for the whole repository.
3. Code to generate for each custom query.
4. Code to generate for each custom result.

In any case, the required steps to extend QueryJ to generate sources based on new templates are:

1. Identify which entity the sources are associated to (see above).
2. Create a Template class extending, respectively,
   1. BasePerTableTemplate
   2. BasePerRepositoryTemplate
3. BasePerCustomSqlTemplate
4. BasePerCustomResultTemplate
5. Create a TemplateGenerator implementing the associated !BasePerXXXTemplateGenerator. This class is responsible of writing the template output to disk.
6. Create a TemplateBuildHandler and TemplateWritingHandler, extending from BasePerXXXTemplateBuildHandler and BasePerXXXTemplateWritingHandler. This two classes participate in QueryJ's Chain of Responsibility. The former takes the input the templates require from the available Command and builds the template instances, whereas the latter asks the decorator to write them.
7. Create a TemplateHandlerBundle using any of the already-existing ones as a model. It's just a composite handler to group the build and writing handlers together.
8. Include the bundle into QueryJ's flow. Extend ''QueryJTask as needed.

Error: Failed to load processor Timestamp

No macro or processor named 'Timestamp' found