|Re: Reasons of the 'Not all members are distinguishable' warning [message #1178456 is a reply to message #1178258]
||Sat, 09 November 2013 17:21
|| Christian Damus
Registered: July 2009
This can be caused not only by the actual owned members of a namespace,
but also imported members that have names clashing with owned members.
This is one reason why element imports can specify aliases.
Unfortunately, the UML2 implementation of the
namespace-members-are-distinguishable constraint doesn't encode in the
problem marker references to the indistinguishable members, so you will
just have to work it out for yourself. You could possibly use an OCL
query to find them. Something like (totally untested) in the context
let ns = self in
ns.members->exists(m | m <> e and not
On 2013-11-09 14:13:14 +0000, Tomas Sandkvist said:
> I'm having trouble to realize where these messages are coming from. How
> hard I look I can't see if there is some element having the same name
> as another, so perhaps that is not the problem?
> Any suggestions appreciated!
> Tomas Sandkvist
Powered by FUDForum
. Page generated in 0.02296 seconds