[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mdt-papyrus.dev] [PROVENANCE INTERNET] Strange issue in Papyrus OCL integration(template signature).
|
... apparently the problem is a type cast (to Class) in class
UML2ASDeclarationSwitch, see:
https://git.eclipse.org/r/plugins/gitiles/ocl/org.eclipse.ocl/+/refs/heads/master/plugins/org.eclipse.ocl.pivot.uml/src/org/eclipse/ocl/pivot/uml/internal/es2as/UML2ASDeclarationSwitch.java#155
I've posted Bug 566594 - [OCL, UML] OCL validation
fails, if the UML model uses non-Class template parameters
Ansgar
On 02/09/2020 09:42, Ansgar Radermacher
wrote:
Hi,
has anyone already seen the following problem with OCL (in a
current Papyrus, but probably since quite a while):
An _expression_ like "self.weight < 5" works fine for a
constraint owned by a class (context) having the integer attribute
weight.
But as soon as I apply any MARTE profile, the xtext editor for OCL
shows multiple errors. I figured out that the problem occurs, as
soon as an element in your model or in an (indirect) import has a
template signature with a classifier template parameter of
meta-class type "DataType" (strangely, there is no problem if the
template parameter is of meta-class type "Class"). In case of
applying a MARTE profile, the problem is caused by the Array and
Interval data types (in the MARTE_DataTypes package that is part
of the MARTE library) having a DataType template parameter.
Any ideas how to fix or work around?
Ansgar
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/mdt-papyrus.dev
.