vendredi 23 octobre 2015

Telosys tools version 3 is comming soon

The Telosys team is working on Telosys tools version 3
It will be a major release with new features, especially the new DSL model.

The DSL is based on a very simple grammar, each entity file will be editable in a specialized Eclipse Editor :

With this DSL it will be possible to define entities from scratch and to generate code without databases

Be patient and stay tuned...

mardi 3 mars 2015

Telosys Tools ver 2.1.1 - What's new ?

The version 2.1.1 comes with interresting new features ...

The generator provides new objects usable in the templates in order to generate native JDBC requests.

These new objects are $jdbcFactory and $jdbc

Example :

With these new objects it's now very easy to generate DAO based on JDBC.

Another object has been added, the $h2 object.

This utility object can be used to generate the DDL for a "create table" statement in a "H2 database"
It has been design to facilitate the generation of JUnit tests using a H2 database "in memory".
Example :

New bundles of templates are available :
  • Java persistence based on native JDBC
  • Java persistence based on Spring JDBC
See these new bundles on GitHub :

The columns comments stored in the database are now available in the model.
The comments are now retrieved from the database and exposed in the model.
They can be used in the templates.
Example : $field.databaseComment

When generating the repository model it's now possible to use "regular expressions" to filter the table names. 
One "regular expression" to "include" and another one to "exclude" table names.
The "regular expressions" are based on the standard Java RegEx provided by the JDK.
Example :

When updating the repository model, the links are now updated when some "foreign keys" have changed in the database

Some bugs have been fixed

Especially the bug regarding duplicated attribute names. In the previous versions when an entity referenced another entity twice the same attribute name was used twice. Now the new system eliminates this risk by adding a number at the end of the name ( ie "author", "author2", "author3", ... )