<node xmlns:BBB="http:SLASHSLASHwww.BBB.orgSLASHBBB"
  xmlns="http:SLASHSLASHwww .AAA.orgSLASHAAA">
 <AAA:something_from_AAA name="xxx" />
 <BBB:something_from_BBB </> </node>

Hi Daniel

I recommend separating your concerns.

Most of the Eclipse Modeling tools support Ecore, and QVTo supports
Ecore to Ecore transformations.

EMF provides XSD import and export capabilities for Ecore files that are
then used by other tools, so find out which of

a) XSD2Ecore
b) Ecore2Ecore
c) Ecore2XSD

does not do as you want and then fix it. Each stage has plenty of
configuration capabilities and opportunities for errors.

Regards

Ed Willink


On 17/10/2011 16:19, daniel.engelhardt wrote:
> Hello,
>
> I would like to write a QVT transformation in Eclipse Indigo that
> accomplishes the following:
>
> I have an Input Meta-Model, lets call it In.ecore (which is generated
> from an xsd file).
>
> I have two Output Meta-Models, Out_includes_A.ecore and
> Out_included_B.ecore, which are also generated from two different xsd
> description files. These xsd files import one another, or to be more
> precise Out_includes_A includes Out_included_B.
> In the Ecore models, I could deal with these references either by
> implementing Attributes of type AnySimpleType or something, or by
> using references to the types in the other Meta-Model. I decided to go
> with the second option, which might be wrong already.
>
> Now, I wrote a QVT transformation that should create an output model
> (out.xmi) something like
>
> <node xmlns:BBB="http:SLASHSLASHwww.BBB.orgSLASHBBB"
> xmlns="http:SLASHSLASHwww .AAA.orgSLASHAAA">
> <something_from_AAA name="xxx" />
> <BBB:something_from_BBB </> </node>
>
>
> However, that's not what I get. Instead, the second namespace is
> completely disregarded (in a sense). I get something like
> <node xmlns="http:SLASHSLASHwww .AAA.orgSLASHAAA">
> <something_from_AAA name="xxx" />
> <BBBsomething_from_BBB </> </node>
>
> where BBBsomething_from_BBB was the name given to the reference
> Element in the node-part of the AAA-Input Meta-Model. The Extended
> Meta Data references are correct (they point to the correct namespace).
>
> The QVT transformation looks like
>
> transformation Input2AAA(in a : Input, out : AAA);
>
> i.e. the Output model is of type AAA, maybe this is my mistake.
>
>
> So, my question is: what do I need to do, to accomplish the behavour I
> want? My problem is, I don't really know where to start. Is it an
> Ecore Problem? Should I somehow try to combine both output metamodels
> into one? Should I use AnyType-based solutions? Or are my Extended
> Meta Data references broken? Or should I go about my QVT
> transformation in a different way? Or is it a problem with the xsd
> importer?
>
> I have worked with all of these tools quite a lot, but my
> understanding of them is not very deep, as one can surely see easily.
> And I left out quite a lot of information. What kind of information
> would you need in order to answer these questions above?
>
> Is there a standard way to go about this? I googled but I could not
> come up with a lot, concerning multiple namespaces in xsd and there
> handling Ecore and in the M2M tooling.
>
> Thank you very much in advance for your help. It is deeply appreciated!
>
> Best regards,
> Daniel