On Nov 15, 2007, at 2: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.
Yes, that is a bit nasty. Just doing the standard EOF Java methods
might be worth it. For the NAME_KEY constants, I just type back in
the old name then refactor it to the new one.
A tough problem.
Chuck
--Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 18:41:35 EST