I'm submitting here the cartridge that I've created for my application
that is not dependent on any EJB.
This cartridge generates code based on the DAO design pattern.
For each entity, the following classes are created:
- a DAO interface that contains CRUD methods
- an implementation of the DAO int
I did read the Andromda vision document these days and I can't remember if this was a concern on that. I believe that performance (speed and memmory) must aways be a concern on the project, since for the user doing all the generation for all the files again and again for really very big productio
Title: Nachricht
Hi
Charles,
there
is no possibility for AndroMDA to detect whether a single model element has
changed (Netbeans MDR does not supply this info). It can only detect whether the
whole model has changed. But this is not what you want,
right?
Sorry...
Matthias
-Ori
Is there any intelligent way for Andromda to NOT re-generate files for unmodified classes in the model? If not, Is this at last a ongoing work in version 3.x?
I'm playing with Andromda 2.x and I'm very happy with him, but that is a limiting problem on doing it for production as model grows over.
