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", ... )

mercredi 2 avril 2014

Telosys Tools 2.1.0 is available

Telosys Tools 2.1.0 is a major version. It comes with some important new features.

Eclipse plugin improvement

The user interface has been improved (more intuitive, less manual operations)

The templates are now organized in "bundles"
A "bundle" is a set of templates, when a bundle is downloaded from GitHub is now immediately available (without any manual installation).
The "generation" process is now possible bundle by bundle

Static resources can been added in a bundle
A bundle can contain "static resources" that are just copied in their destination folder.
It's useful for different kind of static files (.css, .js, .properties, .xml, etc)

New templates

The new templates bundles are available on GitHub

Examples of available stacks :
  • MVC web app based on : Spring MVC + JPA or Spring Data
  • AngularJS web app based on : AngularJS + REST + SpringMVC + JPA or Spring Data
  • RESTfull API services : HATEOAS architecture + Spring Data REST / JPA

New tutorials are available here : 

Telosys Tools Tutorials

NB : the objects exposed in the Velocity context have been modified, then previous templates are not always compatible with this new version

There are now 3 GitHub organizations for the published templates:

jeudi 26 septembre 2013

Telosys Tools 2.0.6 - What's new ?

Packages management :

2 predefined variables have been added ( in "Properties / Telosys Tools : Packages" ) :
  - ${ROOT_PKG}  for the "root package"
  - ${ENTITY_PKG}  for the package where the entities classes are located

Examples for Java :
${ROOT_PKG}  :   ""
${ENTITY_PKG} : ""  ( or "", etc )

If you need other packages variables, they can be defined in the tab "Variables"
With a name like "DAO_PKG", "SERVICE_PKG", etc... ( ending with "_PKG" )

These variables can be used in the templates (.vm files) and in the targets definition ( templates.cfg file ). In the targets each variable ending by "_PKG" and used in the folder definition is transformed into a folder path ( ie : "" becomes "org/foo/bar" ). Hence the package variables can be used to define the destination of the code generation.

Examples in a template  :
  • import ${ROOT_PKG}.cache.${}Cache ;

Examples in targets definition (destination folder) :
  • ${SRC}/${ENTITY_PKG}
  • ${SRC}/${ROOT_PKG}/cache

NB :
For an existing project these two variables must be defined before any code generation. 
(your previous package configuration will be lost )
Check their values in "Properties / Telosys Tools : Packages" after installation of this new version 


Database configuration :

With Telosys Tools 2.0.6 it's no longer useful to define the databases with a text editor (databases.dbcfg file ).

It's now possible to configure databases entirely in the specialised editor (new, update, delete) :


Telosys Tools 2.0.6 Release Preview

Telosys Tools 2.0.6 Release Preview is available

The Eclipse Plugin Update site is here

jeudi 11 juillet 2013

Telosys Tools Forum

In order to facilitate the communication between Telosys Tools users
and developers a forum is open on

Do not hesitate to use it !

Telosys Tools version 2.0.5 is out !

Eclipse plugin version 2.0.5 has been released.

It comes with a template editor and the documentation embedded in Eclipse.

The template editor provides auto-completion

See the screenshots

Install the new plugin from Eclipse Markeplace