> If you disagree, it should be at least push down as subclass of FAMIXNamedEntity.Nope :). An association does not have a name usually.
> What do you think?
I think the issue is relevant, but the problem is that FAMIXAssociation overrides the default source anchor. This method should go away as it is not particularly useful.