Ok that's a good enough reason (to override the initial value)...just didn't know why you need it is all :) File a JIRA issue for it...and if you want feel free to create a patch that does what you describe and I'll apply it.
Quote: my original inclination to define an overridden attribute in the specialization seems to be correct based on my reading of the UML specs (in fact, there is an example of just this). (end of quote) Cool....can you point me to the example? -- Chad Brandon - [EMAIL PROTECTED] http://www.andromda.org _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2955#2955 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
