[great-users] GReAT transformation containing a meta model with nested libraries and namespaces

Kevin Smyth ksmyth at isis.vanderbilt.edu
Fri Mar 7 08:37:24 CST 2014


Hi Tim,

Thanks for the superb description and example. This is a Udm bug. I've 
fixed it, and will make a release that includes the fix soon.

I hope you don't mind that I've included your example in the Udm 
automated tests. If you do mind, I can remove it.

Thanks,
Kevin


On 3/3/2014 6:41 AM, Tim Belschner wrote:
>
> Hello everyone,
>
> I do face an exception when compiling a GReAT transformation which 
> contains a meta model with nested libraries and namespaces respectively.
>
> First, the exception message:
>
> #--------------------------------------------------#
>
> GR Engine v1.7.7.
>
> Copyright (c) 2000-2007 ISIS, Vanderbilt University
>
> Engine Started. Loading relevent files...
>
> Exception: Could not initiliaze Udm Uml Diagram 'MetaLevel3' from GME 
> paradigm: 'MetaLevel3': Cannot resolve association
>
> 'NS_Level2::NS_Level1::Level1_Connection' with rolenames 
> 'srcLevel2_Connection' 'dstLevel2_Connection'
>
> #--------------------------------------------------#
>
> Due to modularity, I nested three meta models as following (attached 
> as libraries):
>
> #--------------------------------------------------#
>
> MetaLevel3
>
> --MetaLevel2 (namespace: NS_Level2)
>
> ----MetaLevel1 (namespace: NS_Level1) (does contain a <<Connection>>)
>
> #--------------------------------------------------#
>
> Whereas MetaLevel2 and 3 are an extension to the next level below. For 
> clarity, I built up a small example (GME 13.8.28.1949): 
> www.ils.uni-stuttgart.de/nested_libraries.zip 
> <http://www.ils.uni-stuttgart.de/nested_libraries.zip>
>
> The compilation is successful except if MetaLevel1 contains a 
> <<Connection>> object.
>
> On the other side, if MetaLevel2 is attached to MetaLevel3 without 
> defining a namespace for it and MetaLevel1 still contains a 
> <<Connection>> object the compiler runs without trouble.
>
> Summing up:
>
> MetaLevel3 with 'NS_Level1::Level1_Connection'
>
> ==> works fine
>
> MetaLevel3 with 'NS_Level2::NS_Level1::Level1_Connection'
>
> ==> seems to violate some restrictions
>
> So my question is:
>
> Is it even possible to use nested meta models and <<Connection>> 
> objects with more than one namespace level?
>
> If my descriptions are two vague, please let me know.
>
> Best Regards
>
> Tim
>
>
>
> _______________________________________________
> great-users mailing list
> great-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/great-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.isis.vanderbilt.edu/pipermail/great-users/attachments/20140307/da432185/attachment.html 


More information about the great-users mailing list