[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.modeling.gmt.amw] question about different forms of amw metamodel and model

hi, guys

I am newbie studying AMW from the samples. However when I looked at 
"Keys2Nested_AMW2ATL" and "Keys2Nested_AMW2XSLT" I found they each defined 
different metamodel and model of the amw transformation.

1. the metamodels are different (though with the same name "mwcore.ecore" ). 
Is it by design in order to serve different purpose? Must it be defined in 
that way in order to support XSLT generation?

2. the models are in differnt forms.  In Keys2Nested_AMW2ATL it is a .amw 
file plus a .prop file, however in Keys2Nested_AMW2XSLT it is a .ecore file. 
I think they are just varies format containing same information, and the 
.amw+.prop formats are just designed to be open from Weaver Editor UI, am I 
correct?
But, since this Keys2Nested_AMW2XSLT the HOT ATL only accept .ecore format 
amw model, I am wondering is there easy way to convert the same amw model 
between .ecore and .amw+.prop format back and force?


Thanks
Leon






-- 
Li Yong (Leon)
Tibco CDC, Worksoft Creative Software Tech. Ltd.
3rd Floor ZPark Build 9th
Hai Dian District
Beijing   P.R.China    (100094)
Tele: (8610) 8282-5266 ext. 8955
Email: yli@xxxxxxxxxxxxxxxxx
li_yong3@xxxxxxxxxxxxx