>>> model and then make all my relationship changes again and regenerate all
>>> affected java again (but maybe I'm just not good at using the tools yet -
>>
>> Personally I don't like all those pesky accessor methods on my EOs. I
>> tend to use EOGenericRecords whenever possible. My Java EOs have ONLY
>> their ivars and businesslogic. Zero accessors. This works BTW. The only
>> price is that instead of doing: firstName() you have to do
>> valueForKey("firstName"). But what I gain is that I basically never have
>> to regen a class, just add/remove the ivar for the EOAttributes that
>> changed. Of course if you do have to merge changes, the FileMerge
>> utility is a pretty cool way to do it.
Maybe since I don't use Java at all in my projects I don't understand all
of the problem. I use custom EO's for almost all of my tables. I have them
in Objective C and I make a different file in my project usually called
ClassExtras into which I put all the methods I like on a Class. The
ClassExtras is a category (I believe this is the correct term) off of
Class. This way when my model can and does change I just regenerate the
code and overwrite. I don't have to deal with the merge tool or any
problems since I dont' customize the code in the file the model generates.
I know that if I needed an ivar in a class instead of just methods I would
have to put that in the main file and have the same merge problems. So far
I have only needed an additional ivar 2 times out of 30+ tables. Even
though you use Java can't your EO's be Obj C??
Bob Stuart
Lockheed Martin
