Open eclipse-qvtd-bot opened 2 weeks ago
By Ed Willink on Dec 11, 2019 13:10
Even if we cannot be positive, we could word better. The already better:
No possible producer of: pivot::TypedElement::type : Type[?]\
can satisfy expression: qvtrProperty.type\
navigation source type: Property\
navigation target type: Type
could be augmented by an 'assumed to be produced by one of:' folowed by a list of Type returning queries.
By Ed Willink on Dec 12, 2019 04:33
Even if we cannot be positive, we could word better. The already better:
No possible producer of: pivot::TypedElement::type : Type[?]\
can satisfy expression: qvtrProperty.type\
navigation source type: Property\
navigation target type: Type
could be augmented by an 'assumed to be produced by one of:' followed by a list of Type returning queries.
| --- | --- | | Bugzilla Link | 546504 | | Status | NEW | | Importance | P3 normal | | Reported | Apr 17, 2019 05:26 EDT | | Modified | Feb 26, 2020 08:28 EDT | | See also | 546271 | | Reporter | Ed Willink |
Description
The new QVTiProductionConsumption design rule check reports that a Property.type is not produced.
The problem is that the Property comes from an opaque helper
query NewATL2QVTr::getProperty(type : mm_oclMM::Type[1], name : String[1]) : mm_oclMM::Property[1];
that locates an 'input' Property whose type matches a parameter.
The Property is in the output qvtr type model, so it must be created somewhere (the helper).
We must therefore have an opaque helper that shows what exists.
Or we have a full loader for the objects that the lookup navigates.
Or we have an opaque output reference model loader...