synchronization and duplicate associations...

[javelin5]

Just recently we were having problems where we created a class diagram.  Then generated code.  After some coding was done it was synchronized to the database.  When the synchronization was complete.  An extra duplicate association showed up everywhere.  We deleted the extra assocation and generated code followed by synchronizing.  They showed up again.  We then deleted the original associations and no more duplicates showed up.  Could someone explain why this happens??

Tim

[pocjoc]

I think this problem comes about because EA does not write out code markers, so after you have either deleted or renamed an attibute/operation or relatipnship, when it comes time to generate the code again, EA does not know the old relationship and therefore does not remove it from the generation and create the new one.  

[mbc]

Pocjoc is right that EA does not support renaming and deletion. If you rename or delete attributes or operations, you must do it manually in both the code and the model. So if you rename a relation attribute in one place, there will be 2 relations after you synchronize. Also note, that if you delete the attribute in EA to correct the problem, also delete the relation in the diagram. I got confused once because 1 relation arrow where directly on top of another in a diagram, so I could only see 1 relation, and I didn't understand why 2 relation attributes where generated in my code.

Mikkel