Hi Marcos,
I understand that xmi:ids are generated by the weaver when I create the
temporary weaving model.
However, the ATL2WTracer receives as input a model and outputs 2 target
models (the traceability model and the woven/target model). My input/woven
model is an UML model and already has the xmi:ids (so I don't need to use
the weaver to create them).
My target/woven model is an instance of an EMF metamodel, and this is the
one that doesn't have xmi:ids. Since this model is created when the
ATL2WTracer is run, the xmi:ids remain Xpointers... regardless if I used
the weaver to set them or not (I'm re-generating the model...). Right?
I'm thinking that I need a way to set up the xmi:ids for the elements in
the target/woven model during the ATL2WTracer transformation, and before I
use the ids to set the references in the traceability model. That's why
I'm asking about extending the XMIResource from EMF plugin.