On Nov 15, 2007, at 3:32 PM, Mike Schrag wrote:
>> I also don't see any advantage (or any good) of being able to
>> generate code from inside of a Java file. It might be useful to
>> have the code generation inside of Entity Modeler though. Then
>> changing an attribute name could refactor the Java code and
>> regenerate.
> I look at this quite often ... It's really really tricky to do
> (mainly BECAUSE those things are eogenerated). You never know
> exactly what dependencies exist without doing analysis on the
> velocity template. For instance, if you rename an attribute, that
> might change some constant to be NEW_NAME_KEY from NAME_KEY, but
> good luck figuring that out. You CAN, it's just not a simple feat.
Personally, of all the possible new EOGeneration features, I would
like selective generation from Entity Modeler (only specific classes)
the most, because I've got a whole bunch of legacy classes in the
EOModel file that I don't want to move into the new EOGenerator
universe yet. So everytime I generate I have to go and delete a whole
bunch of files from the project...
Pierce
This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 18:00:24 EST