Test
The priority is to test all processes from generation to use by end users. Every goodwill is welcome.
- Try Adichatz framework and post a issue or contact us.
- We are looking for specifications of a good idea for a pilot project. Any suggestion will be studied (Current example build on sakila database is too simple to show all the powerful of Adichatz).
Improvement
Documentation
- Adichatz was developed in France. So many errors or inaccuracies stay in website, pdf file or inside plugins. Any help is welcome.
Internationalization
- Adichatz can be internationalized by duplicating files from '{plugin}/resources/bundle' directory.
In '/resources/messages' directory of 'org.adichatz.jpa' plugin, copy files:
- adichatzJpa.properties to adichatzJpa_fr.properties,
- columnPreference.properties to columnPreference_fr.properties,
- …
Then translate values in '*_fr.properties' files.
Security
- Adichatz knows bind the permissions to roles. We do not know the best way to request JBoss AS to obtain authentication and roles. Any help is welcome.
Extensions
Design of Adichatz allows several ways to extend the framework, e.g.:
- UI components : Adichatz proposes many controllers covering many UI component (SWT, nebula). Current controllers can be extended or new UI components can be integrated.
- Today, an implementation of JPA with Hibernate is provided in 'org.adichatz.jpa' plugin. Other implementations can be conceived with an other ORM, another database system (e.g. NoSQL). Any suggestion and help is welcome.
Questions
- Currently, file “persistence.xml” which describes datasource parameters for hibernate is read from file '{binary directory}/META-INF/persistence.xml'. Is it possible to read, by default a file outside the plugin, e.g. in workspace? So that connection parameters could be changed easily in exported final product.