Am 06.04.2017 um 18:41 schrieb Hilaire <hilaire@drgeo.eu>:
Le 06/04/2017 à 16:14, Norbert Hartl a écrit :
One idea will be to have collection of Address, but this really looks strange to me.
why?
It looks like a painful scenario: Address is most of the time referenced by only one object, but in one scenario I need a shared attributes. Because of this it implies to overlook for #save and #remove messages to Address instances all around, forgetting some leading to bugs. But there are not alternative I guess? Or to have two Address class, one set as a root. Not sure what is the best practice.
Not sure either. But I think having a SharedAddress class is worth a try. The other possibility would be if #voyageRoot would be also instance side. Right now I don't have a computer to check. Norbert
Hilaire
-- Dr. Geo http://drgeo.eu