Otherwise the graphical representation is linked with null.
But this additional line causes our eObject (newBehaviorDefinition) to be removed from the laresModel.getBehDefs(), which is a part of our own Meta-Model.
Is there any way to keep the eObject in our own model and to link it to the graphical representation?
With best regards,
Alexander, Mario and Dominik
It deals with separating diagram and domain data into different resources.
Both resources would be loaded into the same reosurce set/editing doamin
inside your editor.
@Andreas: Never thought of that we´re having two models in use...
Can I replace the model of the tutorial with ours anyhow? Or is
it necessary to use both?
At a quick glance, you are creating a dedicated ResourceSet for your laresModel. For cross-referencing to work, your resource should be created in the resourceSet of the Grpahiti Diagram. EMF only can cross ref models in the same resource set.
Added laresModel to the e-resource of the diagram. Now the link-method is working fine with "newBehaviorDefinition" in laresModel!
Now I have to check out if this works with more than one diagram - using the drilldown-feature - as well.