I had similar problem in my large model as well. These unique association end error could be resolved in couple way as I foun dfrom dealing with them:
- For large model it will be very hard to use the model digrams to locate the problematic association so use the relations folder and and use the parent entities to look for the association ends. - COuple reasons for these associations not being unique is that the target/child entity has: (a) other associaton with the same parent and you leftout the association ends (roles) either empty (which in this case it will not be unique or you have used same name. Leaving out empty ends is equivalent to same role name. (b) To keep it safe, just name both ends of the problematic associations and that should solve the problem. I used to have hundereds of similar validation problems in large model but once you find the pattern you can eliminate those problems in few itterations. Safaa -- Safaa Hashim _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3693#3693 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
