Community
Participate
Working Groups
Investigate containment crossing resources boundaries
Created attachment 28134 [details] A zip of patches and an example The zip file contains patches for org.eclipse.emf.ecore, org.eclipse.emf.ecore.xmi, and org.eclipse.emf.codegen.ecore. It also contains an example showing how the new support works. Note that the example contains a Rose model, but the .ecore has been changed since it was generated from the Rose model. The basic idea behind the design is to handle resource containment differently for containment references for which resolveProxies is true. Currently all generated EReferences will have this set to false, regardless of what's in the .ecore. With the new design, the settings will be respected in the generated code. The new design should be a no-op for existing generated models. The idea is that when adding to a containment, if the containment can resovle proxies, the newly contained object will NOT be removed from its directly containing resource.
Created attachment 28170 [details] Proper example for this patch I zipped the wrong example plugins in the previous attachment. This is the right example.
Created attachment 28331 [details] Updated patches relative to latest CVS source Fixing https://bugs.eclipse.org/bugs/show_bug.cgi?id=112330 required source changes that affected this patch set, so I've created a fresh patch set.
Created attachment 28653 [details] A replacement patch for the org.eclipse.emf.ecore.xmi plugin This patch fixes the problem with container reference serialization reported in the newsgroup.
Created attachment 29471 [details] An Eclipse 3.2 multipatch for all the changes relative to the current 2.2 HEAD This is just an updated patch to make it easy to apply the changes against HEAD.
The changes are committed to CVS. And all the tests pass!
Fixed in 2.2.0 I200511240817.
Move to verified as per bug 206558.