|ATL: output xsd [message #82709]
||Thu, 29 May 2008 19:15
Originally posted by: min.kong.morganstanley.com|
1) Is XMI the only output model format supported by ATL rule (NOT query)
2) We have a model-to-model transform goal, where the output model target
is an org.eclipse.xsd instance.
The input model conforms to some input.ecore, and the output model
conforms to an XSD.ecore. Both input and output metamodel are defined in
The output model can ultimately be serialized into an .xsd text file. But
our goal is, not only to get an xsd text file, but to get an *in-memory*
org.eclipse.xsd instance, that conforms to the XSD.ecore.
After experimeting with ATL, it seems that we have only one alternative
- get an out.xmi that conforms to XSD.ecore and "transform" the out.xmi
into an out.xsd text file (with ATL query or another program, which
basically does some string/text processing), and then load that out.xsd
into memory with some org.eclipse.emf.ecore.* and org.eclipse.xsd.*
Is there a more straight-forward way with which we can use ATL to obtain
an in-memory org.eclipse.xsd instance that conforms to the XSD.ecore (the
3) Are there other m2m alternatives you'd suggest for our scenario?
Powered by FUDForum
. Page generated in 0.01676 seconds