Home » Modeling » Epsilon » [HUTN] Problem Linux with property "upper" of the UML.ecore
[HUTN] Problem Linux with property "upper" of the UML.ecore [message #501872] |
Fri, 04 December 2009 08:57 |
Raul Messages: 14 Registered: November 2009 |
Junior Member |
|
|
Hi, I am working with epsilon_0.8.8 in linux and I am using eclipse Ganymede 3.4.0.
I have problem with property "upper" of the model "UML.ecore".
I test the same file in Windows XP and I have not any problem.
Thanks!
This file HUTN shows this error: Reason: Expected UnlimitedNatural for: upper.
@Spec {
metamodel "UML" {
nsUri: "http://www.eclipse.org/uml2/2.1.0/UML"
}
}
uml {
Model "Model1"{
name: "Model1"
nestedPackage: Package "Package1"
}
Package "Package1"{
name: "Package1"
packagedElement: Class "Class1" {name : "Class1"},
Class "Class2" {name : "Class2"},
Association "Association1" {
name : "Association1"
ownedEnd: Property "src1" {
name : "src1"
type : Class "Class1"
upper : -1
lower : 1
},
Property "dst1"{
name : "dst1"
type : Class "Class2"
upper : -1 // FAILS HERE
lower : 1
}
memberEnd: Property "src2", Property "dst2"
},
Property "scr2",
Property "dst2"
}
Property "src2"{
name : "src2"
type : Class "Class1"
upper : -1
lower : 1
}
Property "dst2"{
name : "dst2"
type : Class "Class2"
upper : 1
lower : 1
}
}
[Updated on: Fri, 04 December 2009 09:03] Report message to a moderator
|
|
|
Re: [HUTN] Problem Linux with property "upper" of the UML.ecore [message #501977 is a reply to message #501872] |
Fri, 04 December 2009 16:08 |
Louis Rose Messages: 440 Registered: July 2009 Location: York, United Kingdom |
Senior Member |
|
|
Hi Raul,
Reply below...
Raul wrote on Fri, 04 December 2009 03:57 | Hi, I am working with epsilon_0.8.8 in linux and I am using eclipse Ganymede 3.4.0.
I have problem with property "upper" of the model "UML.ecore".
I test the same file in Windows XP and I have not any problem.
Thanks!
This file HUTN shows this error: Reason: Expected UnlimitedNatural for: upper.
@Spec {
metamodel "UML" {
nsUri: "http://www.eclipse.org/uml2/2.1.0/UML"
}
}
uml {
Model "Model1"{
name: "Model1"
nestedPackage: Package "Package1"
}
Package "Package1"{
name: "Package1"
packagedElement: Class "Class1" {name : "Class1"},
Class "Class2" {name : "Class2"},
Association "Association1" {
name : "Association1"
ownedEnd: Property "src1" {
name : "src1"
type : Class "Class1"
upper : -1
lower : 1
},
Property "dst1"{
name : "dst1"
type : Class "Class2"
upper : -1 // FAILS HERE
lower : 1
}
memberEnd: Property "src2", Property "dst2"
},
Property "scr2",
Property "dst2"
}
Property "src2"{
name : "src2"
type : Class "Class1"
upper : -1
lower : 1
}
Property "dst2"{
name : "dst2"
type : Class "Class2"
upper : 1
lower : 1
}
}
|
The values in the packagedElement slot of Package1 don't look right to me. The first 3 are objects and the last 2 are references to objects. The values in a slot must all be primitives, objects or references, and not a mixture.
Therefore, it seems that the corrected code might be:
@Spec {
metamodel "UML" {
nsUri: "http://www.eclipse.org/uml2/2.1.0/UML"
}
}
uml {
Model "Model1"{
name: "Model1"
nestedPackage: Package "Package1"
}
Package "Package1"{
name: "Package1"
packagedElement: Class "Class1" {name : "Class1"},
Class "Class2" {name : "Class2"},
Association "Association1" {
name : "Association1"
ownedEnd: Property "src1" {
name : "src1"
type : Class "Class1"
upper : -1
lower : 1
},
Property "dst1"{
name : "dst1"
type : Class "Class2"
upper : -1 // FAILS HERE
lower : 1
}
memberEnd: Property "src2", Property "dst2"
},
Property "src2"{
name : "src2"
type : Class "Class1"
upper : -1
lower : 1
},
Property "dst2"{
name : "dst2"
type : Class "Class2"
upper : 1
lower : 1
}
}
}
However, in the version of UML that I'm using (3.0.0), Property is not a subclass of PackagableElement, so I get an error for the above code.
A correct specification for me places the properties inside ownedAttribute slots of the classes, like this:
@Spec {
metamodel "UML" {
nsUri: "http://www.eclipse.org/uml2/2.1.0/UML"
}
}
uml {
Model "Model1"{
name: "Model1"
nestedPackage: Package "Package1"
}
Package "Package1"{
name: "Package1"
packagedElement: Class "Class1" {
name : "Class1"
ownedAttribute: Property "dst2"{
name : "dst2"
type : Class "Class2"
upper : 1
lower : 1
}
},
Class "Class2" {
name : "Class2"
ownedAttribute: Property "src2"{
name : "src2"
type : Class "Class1"
upper : -1
lower : 1
}
},
Association "Association1" {
name : "Association1"
ownedEnd: Property "src1" {
name : "src1"
type : Class "Class1"
upper : -1
lower : 1
},
Property "dst1"{
name : "dst1"
type : Class "Class2"
upper : -1 // FAILS HERE
lower : 1
}
memberEnd: Property "src2", Property "dst2"
}
}
}
The error message that you received seems counter-intuitive. I will investigate, and see if we can produce a better error message when mixed values are provided for a slot.
Hope this helps,
Louis.
|
|
| | | | | | | | |
Re: [HUTN] Problem Linux with property "upper" of the UML.ecore [message #583432 is a reply to message #501872] |
Fri, 04 December 2009 16:08 |
Louis Rose Messages: 440 Registered: July 2009 Location: York, United Kingdom |
Senior Member |
|
|
Hi Raul,
Reply below...
Raul wrote on Fri, 04 December 2009 03:57
> Hi, I am working with epsilon_0.8.8 in linux and I am using eclipse Ganymede 3.4.0.
> I have problem with property "upper" of the model "UML.ecore".
> I test the same file in Windows XP and I have not any problem.
> Thanks!
>
> This file HUTN shows this error: Reason: Expected UnlimitedNatural for: upper.
>
> @Spec {
> metamodel "UML" {
> nsUri: "http://www.eclipse.org/uml2/2.1.0/UML"
> }
> }
>
> uml {
> Model "Model1"{
> name: "Model1"
> nestedPackage: Package "Package1"
> }
>
> Package "Package1"{
> name: "Package1"
> packagedElement: Class "Class1" {name : "Class1"},
> Class "Class2" {name : "Class2"},
> Association "Association1" {
> name : "Association1"
> ownedEnd: Property "src1" {
> name : "src1"
> type : Class "Class1"
> upper : -1
> lower : 1
> },
> Property "dst1"{
> name : "dst1"
> type : Class "Class2"
> upper : -1 // FAILS HERE
> lower : 1
> }
> memberEnd: Property "src2", Property "dst2"
> },
> Property "scr2",
> Property "dst2"
> }
>
> Property "src2"{
> name : "src2"
> type : Class "Class1"
> upper : -1
> lower : 1
> }
>
> Property "dst2"{
> name : "dst2"
> type : Class "Class2"
> upper : 1
> lower : 1
> }
>
> }
The values in the packagedElement slot of Package1 don't look right to me. The first 3 are objects and the last 2 are references to objects. The values in a slot must all be primitives, objects or references, and not a mixture.
Therefore, it seems that the corrected code might be:
@Spec {
metamodel "UML" {
nsUri: "http://www.eclipse.org/uml2/2.1.0/UML"
}
}
uml {
Model "Model1"{
name: "Model1"
nestedPackage: Package "Package1"
}
Package "Package1"{
name: "Package1"
packagedElement: Class "Class1" {name : "Class1"},
Class "Class2" {name : "Class2"},
Association "Association1" {
name : "Association1"
ownedEnd: Property "src1" {
name : "src1"
type : Class "Class1"
upper : -1
lower : 1
},
Property "dst1"{
name : "dst1"
type : Class "Class2"
upper : -1 // FAILS HERE
lower : 1
}
memberEnd: Property "src2", Property "dst2"
},
Property "src2"{
name : "src2"
type : Class "Class1"
upper : -1
lower : 1
},
Property "dst2"{
name : "dst2"
type : Class "Class2"
upper : 1
lower : 1
}
}
}
However, in the version of UML that I'm using (3.0.0), Property is not a subclass of PackagableElement, so I get an error for the above code.
A correct specification for me places the properties inside ownedAttribute slots of the classes, like this:
@Spec {
metamodel "UML" {
nsUri: "http://www.eclipse.org/uml2/2.1.0/UML"
}
}
uml {
Model "Model1"{
name: "Model1"
nestedPackage: Package "Package1"
}
Package "Package1"{
name: "Package1"
packagedElement: Class "Class1" {
name : "Class1"
ownedAttribute: Property "dst2"{
name : "dst2"
type : Class "Class2"
upper : 1
lower : 1
}
},
Class "Class2" {
name : "Class2"
ownedAttribute: Property "src2"{
name : "src2"
type : Class "Class1"
upper : -1
lower : 1
}
},
Association "Association1" {
name : "Association1"
ownedEnd: Property "src1" {
name : "src1"
type : Class "Class1"
upper : -1
lower : 1
},
Property "dst1"{
name : "dst1"
type : Class "Class2"
upper : -1 // FAILS HERE
lower : 1
}
memberEnd: Property "src2", Property "dst2"
}
}
}
The error message that you received seems counter-intuitive. I will investigate, and see if we can produce a better error message when mixed values are provided for a slot.
Hope this helps,
Louis.
|
|
| | | | | | | |
Goto Forum:
Current Time: Wed Apr 24 14:56:29 GMT 2024
Powered by FUDForum. Page generated in 0.04727 seconds
|