Hi, Here is another scenario where I have trouble with Voyage: Let's an object A, with an attribute an object Address. Then I create B, a copy of A. Of course the object Address is both an attribute of A and B. (no deep copy). As long as my Voyage repo is running, editing Address from A or B is doing fine: when editing Address from A, I can see this reflected in B's Address, as expected. Sadly, this Object scheme is lost in the persistency: when I reset the repo, shutdown it, restart it, to force a full retrieve from the Mongo repo, object A and B do not share anymore the Address object has it should be. I understand Voyage is not a true really Object Oriented repository, but is it possible to overcome such limitation? One idea will be to have collection of Address, but this really looks strange to me. I think Fuel was doing just fine with such scenario, but sadly Fuel is not reliable between images. Thanks to read up to here. Hilaire -- Dr. Geo http://drgeo.eu