search

eclipse-qvtd / org.eclipse.qvtd

Eclipse Public License 2.0
0 stars 0 forks source link

The Property Dependency analysis shows a supertype.property dependency instead of actual type #105

Open eclipse-qvtd-bot opened 1 week ago

eclipse-qvtd-bot commented 1 week ago

| --- | --- | | Bugzilla Link | 465834 | | Status | NEW | | Importance | P3 normal | | Reported | Apr 29, 2015 11:21 EDT | | Modified | Apr 29, 2015 11:35 EDT | | Version | 1.0 | | Reporter | Horacio Hoyos |

Description

In the /org.eclipse.qvtd.build.etl.tests/src/org/eclipse/qvtd/build/etl/tests/UmlToRdbms/UmlToRdbms.qvtc example, for the primitive type MR mappings (e.g. booleanToBoolean_MR), there is a dependency to PrimitiveToName.owner. Since the mapping has a variable of a specific subtype, e.g. BooleanToBoolean, the dependency should be shown as BooleanToBoolean.owner .

eclipse-qvtd-bot commented 1 week ago

By Horacio Hoyos on Apr 29, 2015 11:31

Similarly, in the opposite case, i.e. the mapping has an input of a type which has subtypes, the property dependencies should be to the given property of all subtypes. Yes, the types are connected by inheritance edges, but this is not true for the properties. This causes propertyes form (abstract) supertypes to be shown in the graph only as requirements, but there is no mapping that produces them.

eclipse-qvtd-bot commented 1 week ago

By Horacio Hoyos on Apr 29, 2015 11:35

(In reply to Horacio Hoyos from comment #1)

Similarly, in the opposite case, i.e. the mapping has an input of a type which has subtypes, the property dependencies should be to the given property of all subtypes. Yes, the types are connected by inheritance edges, but this is not true for the properties. This causes propertyes form (abstract) supertypes to be shown in the graph only as requirements, but there is no mapping that produces them.

Disregard this comment please. The behaviour is the same as originally posted, but this is the effect it has on productions.