Eclipse Community Forums: GMT (Generative Modeling Technologies) » [Epsilon] Problems using HUTN with UML metamodel

Help

Home

Home » Archived » GMT (Generative Modeling Technologies) » [Epsilon] Problems using HUTN with UML metamodel

Show: Today's Messages :: Show Polls :: Message Navigator

[Epsilon] Problems using HUTN with UML metamodel [message #383922]

Tue, 01 July 2008 07:58

Pau Giner

Messages: 18
Registered: July 2009

Junior Member

Hello,
I've experienced problems with HUTN when trying to define a UML model.
The problem I guess is that UML metamodel uses its own dataTypes. So
HUTN cannot convert strings to the UML-defined String datatype.

For example, if I define the following:

@Spec {
MetaModel "uml" {
nsUri = "http://www.eclipse.org/uml2/2.1.0/UML"
}
}

Packages {
Package "Pk" {
name: "package"
nestedPackage: Profile "Pr" { name: "profile" }
ownedType: Class "C" { name: "class" }
}
}

I get the following error:

[Line: 9, Column: 5, Reason: Expected String for: name, Line: 10,
Column: 35, Reason: Expected String for: name, Line: 11, Column: 28,
Reason: Expected String for: name]

Is there any construct to handle the creation of these datatypes?

--Pau

Report message to a moderator

Re: [Epsilon] Problems using HUTN with UML metamodel [message #383924 is a reply to message #383922]

Wed, 02 July 2008 09:54

Louis Rose

Messages: 440
Registered: July 2009
Location: York, United Kingdom

Senior Member

Hi Pau,

I've been able to recreate this problem.

I'll investigate further and post a reply later today.

Many thanks,
Louis.

Pau Giner wrote:
> Hello,
> I've experienced problems with HUTN when trying to define a UML model.
> The problem I guess is that UML metamodel uses its own dataTypes. So
> HUTN cannot convert strings to the UML-defined String datatype.
>
>
> For example, if I define the following:
>
> @Spec {
> MetaModel "uml" {
> nsUri = "http://www.eclipse.org/uml2/2.1.0/UML"
> }
> }
>
> Packages {
> Package "Pk" {
> name: "package"
> nestedPackage: Profile "Pr" { name: "profile" }
> ownedType: Class "C" { name: "class" }
> }
> }
>
>
>
> I get the following error:
>
> [Line: 9, Column: 5, Reason: Expected String for: name, Line: 10,
> Column: 35, Reason: Expected String for: name, Line: 11, Column: 28,
> Reason: Expected String for: name]
>
> Is there any construct to handle the creation of these datatypes?
>
> --Pau

Report message to a moderator

Re: [Epsilon] Problems using HUTN with UML metamodel [message #383933 is a reply to message #383922]

Wed, 02 July 2008 16:37

Louis Rose

Messages: 440
Registered: July 2009
Location: York, United Kingdom

Senior Member

This is a multi-part message in MIME format.
--------------060804040005050204060001
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Pau,

As you anticipated, the problem was caused by UML2 using different
datatypes to Ecore. We've fixed the issue by validating against the
underlying Java datatype, rather than the Ecore datatype.

We're currently undergoing migration activities with Epsilon, so we're
not interacting with the CVS server. So I've attached a fix to this
message. To apply the fix, you'll need to:

1) Close Eclipse

2) Locate the HUTN engine plugin JAR in your Eclipse installation.
Usually called: <<eclipse
location>>/plugins/org.epsilon.hutn.engine_1.0.1.jar

3) Unzip the HUTN engine plugin JAR, and overlay the binary code
directory with the archive file attached to this message.

4) Create a new JAR file from the overlay, and replace the
org.epsilon.hutn.engine_1.0.1.jar

5) Restart Eclipse

Let us know if this fixes the problem, if you need any clarification on
how to overlay the attachment.

If you could also open a bug report on the GMT buzilla website
( http://dev.eclipse.org/bugs/buglist.cgi?product=gmt&cmdt ype=doit&order=Reuse+same+sort+as+last+time),
we'll then patch Epsilon once our CVS migration has been completed. Thanks!

Many thanks,
Louis.

Pau Giner wrote:
> Hello,
> I've experienced problems with HUTN when trying to define a UML model.
> The problem I guess is that UML metamodel uses its own dataTypes. So
> HUTN cannot convert strings to the UML-defined String datatype.
>
>
> For example, if I define the following:
>
> @Spec {
> MetaModel "uml" {
> nsUri = "http://www.eclipse.org/uml2/2.1.0/UML"
> }
> }
>
> Packages {
> Package "Pk" {
> name: "package"
> nestedPackage: Profile "Pr" { name: "profile" }
> ownedType: Class "C" { name: "class" }
> }
> }
>
>
>
> I get the following error:
>
> [Line: 9, Column: 5, Reason: Expected String for: name, Line: 10,
> Column: 35, Reason: Expected String for: name, Line: 11, Column: 28,
> Reason: Expected String for: name]
>
> Is there any construct to handle the creation of these datatypes?
>
> --Pau

--------------060804040005050204060001
Content-Type: application/zip;
name="hutn-uml2-fix.zip"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="hutn-uml2-fix.zip"

UEsDBBQAAAAIAKhd4jiLNwZ0hQMAADoUAAA/ABUAb3JnL2Vwc2lsb24vaHV0 bi92YWxpZGF0
aW9uL21vZGVsL1ZhbGlkYXRlSW50ZXJtZWRpYXRlTW9kZWwuZXZsVVQJAAM7 XGtIPFxrSFV4
BADoCAoA7VhLU9swED6TX6Ge4gwznvaaTA88wgwHygyB9qzIa0egSK4lUyjk v3cli1hxnJCk
BC6cGOzV7n4PKVozJQ08GHIiqNaX41tghjx1DjoHTEltCsqlIecJSMNTDoW+ KLU5hhvJf5dg
4w6ykhZJn2gQaczncTHXp5ByCUnUwyA2AXbXFlQlqvO76CloTTPok+5pmQvO qAFSr8LH5LCZ
qnMwa/Ts8Lh3tuXhA9cm7HdC9SgHhgHsAgydqgRE2Or84ZdhnSmmQpxjBSoZ 6KgXYxNIV8Se
WSzpFMj3qi3zmAO+5H8h6uGzbwuQbmQBTGWSa0gIm6cOUNnlFs+s02FenJFQ rvsA3xlQUxaw
BThCZVJVUH+kY/8aK12mUSD9clCtllE1Ewg+ULhelFZdLbxs6P9aXjgSYmSK kmEiKjxMvYpr
X3Azun1wwLV/0qTbFFxm60k/YgxyU0XqpZ2gqeEaAemo2xSq29wQRi3BtTRY cWLu3Wb/+VHB
7t7SexoLKrO4qt5dADx8QOUNgq39tCa/o/IQY1NVtNOyuKtGWE/ATypKSHyu EyqlMtf0DiEK
w3P/eh+ccH1B5SOqrIoq7N5VctovKf/SDamCCDZJciim3Fh2VuINbHCOfzIo NvGBD/0oI/jy
3Tkx26ZCUJ822pONzoSiZhMTucCPspArvruBUrf800L7sdCxUgKo3MREPvSj bOTL726ksU/w
aaX9WOkKUigASW8x0/xd0rjx1zfM9pu8jrE03tsi/sxbb/W91Zey1pt9BiZo ob5q82eLeEWN
mJroa8/ifR9562tvELaew109EVL9lsbYTP5jnBKueDYxdnu9A0eti7aQcYnl Vqe+eo4wNc2x
/ljAL24mEW9MKr1aniW7blIkgXGZNbfGW590KLFCHyAMJVfNhf2X3xcrbQG4 VBIb1xx33faK
pb4puI6R+OE0N2jSQWdGwirVVELatmhrqWD8XDNg1xL60S8c+QaLON3R1sob WZjslwJsV/e0
COZysuJTAOl//69vBNUUXH0pcLwO5nysa3DD7N4Abh/VWFaN1lwyUSaYj/Xm zcxaFF20/0pm
2jj0GZC0ndWu3GcZa6VqGwXq1trxtuNqHAeve6Rhd56SYJH7CUtePpL0yBPx mFIqNAzIbA7S
wl9ouv5V0KMSm/afcQJUDTxH8pH402aDDeBS56iXEdLu7upBdeAEj2f/AFBL AwQUAAAACADL
XuI4lpgFgvMBAABLBgAATAAVAG9yZy9lcHNpbG9uL2h1dG4vZ2VuZXJhdGUv bW9kZWwvR2Vu
ZXJhdGVJbnRlcm1lZGlhdGUyTW9kZWxUcmFuc2Zvcm1hdGlvbi5lZ2xVVAkA A15ea0j2q2tI
VXgEAOgICgCVVLFu2zAQnamvuAQwIi1E0VGFhyRtgQxBgWY0OjDSyWBBkylJ FTBS/3uPlChL
cuQ4kwjq3XuP747crKAxFvJKCedAavh2H1ZcKPWgnRe6QpcXBbzC6ldmW4Xw 4/k3Vv7zZrWO
NVyLHdI/AG+FdkS2AwMlPGiPdoe1FB6vImdXGIAGPCEeTY3qasYDrxnL2LYV ti7BcL9/QVjD
zQx1Q6BN71x4b+Vz6zG470B4q9Rt2na9eSYbyA3fon9Sxt/tv6PwrcU8cA8c ib/g0n3FRmqs
4+kzxkgvMByh0j0KvR/CYYxFP3+FaqOXy7ViietkGPP8+g3YNRd13ZEXXwLu 0Hk6ACqHg4WF
YijXH/bDhc8/Ra0oE/gPWVoO8Vts0CKNyTT+n2n7kvgHjvfjP0IX4q+Oo3am CW8oEm40pi7p
pkjnFV0/Rmoc/7SSkkPtqfbdFp3wnWnRJW67bk1MLLRu1ETzglZ4afT0uvbx nXhpui/d3Sea
Gb0t5vc8wENqFgmnwaFquKM9x2lJlLkrT/H/wPHEvIZ+VaTpO4xdDlMVC08y CMYogDiNMxey
pkhkI9E6XhkVzciyOwY5kLNAYwcn0vdGeyH1jmg+LG46TArBlEuPIznxNl7w iXZvc27xzCs7
crAEmT3xyVx1zlw1ypF6FQ53bNR/UEsBAhcDFAAAAAgAqF3iOIs3BnSFAwAA OhQAAD8ADQAA
AAAAAQAAAKSBAAAAAG9yZy9lcHNpbG9uL2h1dG4vdmFsaWRhdGlvbi9tb2Rl bC9WYWxpZGF0
ZUludGVybWVkaWF0ZU1vZGVsLmV2bFVUBQADO1xrSFV4AABQSwECFwMUAAAA CADLXuI4lpgF
gvMBAABLBgAATAANAAAAAAABAAAApIH3AwAAb3JnL2Vwc2lsb24vaHV0bi9n ZW5lcmF0ZS9t
b2RlbC9HZW5lcmF0ZUludGVybWVkaWF0ZTJNb2RlbFRyYW5zZm9ybWF0aW9u LmVnbFVUBQAD
Xl5rSFV4AABQSwUGAAAAAAIAAgABAQAAaQYAAAAA
--------------060804040005050204060001--

Report message to a moderator

Re: [Epsilon] Problems using HUTN with UML metamodel [message #383936 is a reply to message #383933]

Thu, 03 July 2008 11:12

Pau Giner

Messages: 18
Registered: July 2009

Junior Member

Hello,

I applied the patch and now UML models can be generated (I tried the
example I commented in the previous mail). However, I discovered another
problem, a kind of name collision:

The UML example I use works depending wether another metamode (namely X)
is registered.

The key point is that in metamodel X I have defined metaclases named
"Class" and "Package". So when metamodel X is registered this metaclases
are the ones HUTN is trying to use despite I indicate in the @Spec of
the example that I'm using the UML metamodel.

So, before registering X, the model is generated, but after it I get
this error:

org.epsilon.hutn.exceptions.HutnGenerationException: Property
'ownedType' not found in object
org.eclipse.emf.ecore.impl.DynamicEObjectImpl@356eb0 [eClass:
org.eclipse.emf.ecore.impl.EClassImpl@18380a4 [name: Package]
[instanceClassName: null] [abstract: false, interface: false]] (152:4)

Restricting the used classes to the indicated namespace can be a
solution. However, considering that there are metamodels that import (or
extend) elements from different metamodels, the solution maybe is not so
easy.

In any case the problem now seems that it is not UML-specific, but
related to the way HUTN looks for metaclasses.

--Pau Giner

Louis Rose escribió:
> Hi Pau,
>
> As you anticipated, the problem was caused by UML2 using different
> datatypes to Ecore. We've fixed the issue by validating against the
> underlying Java datatype, rather than the Ecore datatype.
>
> We're currently undergoing migration activities with Epsilon, so we're
> not interacting with the CVS server. So I've attached a fix to this
> message. To apply the fix, you'll need to:
>
> 1) Close Eclipse
>
> 2) Locate the HUTN engine plugin JAR in your Eclipse installation.
> Usually called: <<eclipse
> location>>/plugins/org.epsilon.hutn.engine_1.0.1.jar
>
> 3) Unzip the HUTN engine plugin JAR, and overlay the binary code
> directory with the archive file attached to this message.
>
> 4) Create a new JAR file from the overlay, and replace the
> org.epsilon.hutn.engine_1.0.1.jar
>
> 5) Restart Eclipse
>
> Let us know if this fixes the problem, if you need any clarification on
> how to overlay the attachment.
>
> If you could also open a bug report on the GMT buzilla website
> ( http://dev.eclipse.org/bugs/buglist.cgi?product=gmt&cmdt ype=doit&order=Reuse+same+sort+as+last+time),
> we'll then patch Epsilon once our CVS migration has been completed. Thanks!
>
> Many thanks,
> Louis.
>
>
>
> Pau Giner wrote:
>> Hello,
>> I've experienced problems with HUTN when trying to define a UML model.
>> The problem I guess is that UML metamodel uses its own dataTypes. So
>> HUTN cannot convert strings to the UML-defined String datatype.
>>
>>
>> For example, if I define the following:
>>
>> @Spec {
>> MetaModel "uml" {
>> nsUri = "http://www.eclipse.org/uml2/2.1.0/UML"
>> }
>> }
>>
>> Packages {
>> Package "Pk" {
>> name: "package"
>> nestedPackage: Profile "Pr" { name: "profile" }
>> ownedType: Class "C" { name: "class" }
>> }
>> }
>>
>>
>>
>> I get the following error:
>>
>> [Line: 9, Column: 5, Reason: Expected String for: name, Line: 10,
>> Column: 35, Reason: Expected String for: name, Line: 11, Column: 28,
>> Reason: Expected String for: name]
>>
>> Is there any construct to handle the creation of these datatypes?
>>
>> --Pau
>

Report message to a moderator

Re: [Epsilon] Problems using HUTN with UML metamodel [message #383942 is a reply to message #383936]

Fri, 04 July 2008 16:51

Louis Rose

Messages: 440
Registered: July 2009
Location: York, United Kingdom

Senior Member

This is a multi-part message in MIME format.
--------------040209090309010600010809
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi Pau,

I'm glad that the first fix worked. Many thanks for this bug report.

This time, the problem was caused by us neglecting to inspect the nsUri
specified in the Spec section in the final model generator phase. This
has now been fixed.

CVS migration activities are still occuring for Epsilon, so I'm afraid
we have to ask you to overlay your HUTN engine JAR file once again.
Please find attached a new fix.

Both this fix and the previous one, will appear in the next release of
HUTN, which we will produce subsequent to the completion of the CVS
migration activities.

I thought it best to mention that I'll be on vacation for the next
couple of weeks, and I won't be checking the newsgroup for the next 10
days. Should you have any further problems, I'll be in contact as soon
as I return.

Many thanks,
Louis.

Pau Giner wrote:
> Hello,
>
> I applied the patch and now UML models can be generated (I tried the
> example I commented in the previous mail). However, I discovered another
> problem, a kind of name collision:
>
> The UML example I use works depending wether another metamode (namely X)
> is registered.
>
> The key point is that in metamodel X I have defined metaclases named
> "Class" and "Package". So when metamodel X is registered this metaclases
> are the ones HUTN is trying to use despite I indicate in the @Spec of
> the example that I'm using the UML metamodel.
>
>
> So, before registering X, the model is generated, but after it I get
> this error:
>
> org.epsilon.hutn.exceptions.HutnGenerationException: Property
> 'ownedType' not found in object
> org.eclipse.emf.ecore.impl.DynamicEObjectImpl@356eb0 [eClass:
> org.eclipse.emf.ecore.impl.EClassImpl@18380a4 [name: Package]
> [instanceClassName: null] [abstract: false, interface: false]] (152:4)
>
>
> Restricting the used classes to the indicated namespace can be a
> solution. However, considering that there are metamodels that import (or
> extend) elements from different metamodels, the solution maybe is not so
> easy.
>
> In any case the problem now seems that it is not UML-specific, but
> related to the way HUTN looks for metaclasses.
>
>
>
> --Pau Giner
>
>
> Louis Rose escribi

Report message to a moderator

Re: [Epsilon] Problems using HUTN with UML metamodel [message #383945 is a reply to message #383942]

Mon, 07 July 2008 08:57

Pau Giner

Messages: 18
Registered: July 2009

Junior Member

Ok, now it works.

Thanks for the fix,
and enjoy your hollydays.

--Pau

Louis Rose escribió:
> Hi Pau,
>
> I'm glad that the first fix worked. Many thanks for this bug report.
>
> This time, the problem was caused by us neglecting to inspect the nsUri
> specified in the Spec section in the final model generator phase. This
> has now been fixed.
>
> CVS migration activities are still occuring for Epsilon, so I'm afraid
> we have to ask you to overlay your HUTN engine JAR file once again.
> Please find attached a new fix.
>
> Both this fix and the previous one, will appear in the next release of
> HUTN, which we will produce subsequent to the completion of the CVS
> migration activities.
>
> I thought it best to mention that I'll be on vacation for the next
> couple of weeks, and I won't be checking the newsgroup for the next 10
> days. Should you have any further problems, I'll be in contact as soon
> as I return.
>
> Many thanks,
> Louis.
>
> Pau Giner wrote:
>> Hello,
>>
>> I applied the patch and now UML models can be generated (I tried the
>> example I commented in the previous mail). However, I discovered
>> another problem, a kind of name collision:
>>
>> The UML example I use works depending wether another metamode (namely
>> X) is registered.
>>
>> The key point is that in metamodel X I have defined metaclases named
>> "Class" and "Package". So when metamodel X is registered this
>> metaclases are the ones HUTN is trying to use despite I indicate in
>> the @Spec of the example that I'm using the UML metamodel.
>>
>>
>> So, before registering X, the model is generated, but after it I get
>> this error:
>>
>> org.epsilon.hutn.exceptions.HutnGenerationException: Property
>> 'ownedType' not found in object
>> org.eclipse.emf.ecore.impl.DynamicEObjectImpl@356eb0 [eClass:
>> org.eclipse.emf.ecore.impl.EClassImpl@18380a4 [name: Package]
>> [instanceClassName: null] [abstract: false, interface: false]] (152:4)
>>
>>
>> Restricting the used classes to the indicated namespace can be a
>> solution. However, considering that there are metamodels that import
>> (or extend) elements from different metamodels, the solution maybe is
>> not so easy.
>>
>> In any case the problem now seems that it is not UML-specific, but
>> related to the way HUTN looks for metaclasses.
>>
>>
>>
>> --Pau Giner
>>
>>
>> Louis Rose escribió:
>>> Hi Pau,
>>>
>>> As you anticipated, the problem was caused by UML2 using different
>>> datatypes to Ecore. We've fixed the issue by validating against the
>>> underlying Java datatype, rather than the Ecore datatype.
>>>
>>> We're currently undergoing migration activities with Epsilon, so
>>> we're not interacting with the CVS server. So I've attached a fix to
>>> this message. To apply the fix, you'll need to:
>>>
>>> 1) Close Eclipse
>>>
>>> 2) Locate the HUTN engine plugin JAR in your Eclipse installation.
>>> Usually called: <<eclipse
>>> location>>/plugins/org.epsilon.hutn.engine_1.0.1.jar
>>>
>>> 3) Unzip the HUTN engine plugin JAR, and overlay the binary code
>>> directory with the archive file attached to this message.
>>>
>>> 4) Create a new JAR file from the overlay, and replace the
>>> org.epsilon.hutn.engine_1.0.1.jar
>>>
>>> 5) Restart Eclipse
>>>
>>> Let us know if this fixes the problem, if you need any clarification
>>> on how to overlay the attachment.
>>>
>>> If you could also open a bug report on the GMT buzilla website
>>> ( http://dev.eclipse.org/bugs/buglist.cgi?product=gmt&cmdt ype=doit&order=Reuse+same+sort+as+last+time),
>>> we'll then patch Epsilon once our CVS migration has been completed.
>>> Thanks!
>>>
>>> Many thanks,
>>> Louis.
>>>
>>>
>>>
>>> Pau Giner wrote:
>>>> Hello,
>>>> I've experienced problems with HUTN when trying to define a UML
>>>> model. The problem I guess is that UML metamodel uses its own
>>>> dataTypes. So HUTN cannot convert strings to the UML-defined String
>>>> datatype.
>>>>
>>>>
>>>> For example, if I define the following:
>>>>
>>>> @Spec {
>>>> MetaModel "uml" {
>>>> nsUri = "http://www.eclipse.org/uml2/2.1.0/UML"
>>>> }
>>>> }
>>>>
>>>> Packages {
>>>> Package "Pk" {
>>>> name: "package"
>>>> nestedPackage: Profile "Pr" { name: "profile" }
>>>> ownedType: Class "C" { name: "class" }
>>>> }
>>>> }
>>>>
>>>>
>>>>
>>>> I get the following error:
>>>>
>>>> [Line: 9, Column: 5, Reason: Expected String for: name, Line: 10,
>>>> Column: 35, Reason: Expected String for: name, Line: 11, Column: 28,
>>>> Reason: Expected String for: name]
>>>>
>>>> Is there any construct to handle the creation of these datatypes?
>>>>
>>>> --Pau
>>>
>

Report message to a moderator