Best practice code generation

[mschipperheyn]

Hi,

Is there a best practice or official way of doing things with regards to code generation. As described in previous posts there are some issues when you update the model and want to synchronize with code modified through an editor. Also, you seem to need to generate added classes in the model manually.

What is the best way of working with code generation?
Some givens in my mind are :

*code gets generated to package structures
*models get updated and need to synchronize with externally modified code
*code gets updated and needs to synchronize with the model
*when a package structure and the directory it is located at for code generation is known, you don't want to manually specify the output location for newly added classes in the model
* code should not be overwritten without warning in code generation
* when conflicts arise in the code generation process with regards to existing code, some kind of merge like function should highlight the issues and prevent code loss (compare cvs and subversion)

In the end, I'm looking for a sort of seemless integration. So, if any tips are available on making this process as painless as possible?

Kind regards,

Marc

[Hans]

Hi Marc,

unfortunately, there's right now no support on this: we're right now on our own.
I am with you: We should all be able to get at a seemless solution for ourselves. And the best way to achieve this is through a topic in this forum in which we are allowed to bring in and let be discussed our little code templates.

Regards
Detlef