You're right: you can't have the same attribute on a specialization if it already exists in the parent class, thus far we haven't seen any reason to have this...why would you want to if its in the super class anyway?
Also you can go more than two levels of inheritance when retrieving the attributes (this keeps traveling up the hierarchy by calling superClass.getGeneralization()): Collection attributes = this.getAttributes(); for (ClassifierFacade superClass = (ClassifierFacade)getGeneralization(); superClass != null && follow; superClass = (ClassifierFacade)superClass.getGeneralization()) { attributes.addAll(superClass.getAttributes()); } return attributes; or were you referring to something else? -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2953#2953 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
