Plane info linkage problems

[cxallan]

Currently, the linkage between PlaneInfo? and Pixels is not preserved (the PlaneInfo? objects are totally orphaned and not saved) when using the following:

PlaneInfo planeInfo = new PlaneInfo();
planeInfo.setPixels(pixels);
iUpdate.save(pixels);

It is preserved when using this however:

PlaneInfo planeInfo = new PlaneInfo();
pixels.addToPlaneInfo(planeInfo);
iUpdate.save(pixels);

As far as I can recall from previous discussions with Josh on similar problems, this has to do with the sort of explicit "double-linking" that needs to take place with the objects to preserve linkages when traversing up or down the graph. Is this "double-linking" supposed to happen here or is it simply a case of using the API properly?

[jmoore]

The double-linking currently only happens on the addToXYZ method calls. Conceivably, we could add that logic to the setABC methods as well, but it entails a search through the existing collection, forcing us to be careful because of the tempermental equals logic on the client-side (possibly fixed by #54)

The broken, first example given above :

PlaneInfo planeInfo = new PlaneInfo();
planeInfo.setPixels(pixels);
iUpdate.save(pixels);

can be easily fixed, though, by saving the PlaneInfo instance rather than the Pixels:

  Pixels pixels = ObjectFactory.createPixelGraph(null);
  PlaneInfo planeInfo = createPlaneInfo();
  planeInfo.setPixels(pixels);
  planeInfo = (PlaneInfo) iUpdate.saveAndReturnObject(planeInfo);

r722 provides some examples. See TicketsUpTo199Test.

Passing this back to you for a recommendation on what needs to be fixed for the API consumer. Perhaps just becomes a documentation bug.

[jmoore]

This has been settled. Closing.