Le 06/11/2017 à 18:02, Tudor Girba a écrit :
Hi,My problem is that: I know that a children selector will return aFAMIXSourcedEntity and I need to send some messages toFAMIXSourcedEntity that are in the Trait. But FAMIXSourcedEntity cannotuse the Trait if we do not accept that the associations will also getthe Trait.If we introduce this FAMIXNonAssociationEntity then we will move#comments and #containerFiles to this entity? Also FAMIXFile>>entitiesshould point to FAMIXNonAssociationEntity?
The point of Traits is exactly to not require inheritance.
Why is it not good solution to add TEntityMetaLevelDependency to all classes that require it regardless of the place in inheritance?
But once again… Why an association car understand
#atScope:/#children/#parents (which are queries) and not #queryAllIncoming?
I don’t remember why. Perhaps it is a design error.
I would have to make some test to have be sure. But no time to do it in the next two weeks at least or even more. Sorry.
If you want, try to remove TMetaLevelDependencies in the traits used by TAssociationMetaLevelDependency.