Staz . wrote:
This is an interesting solution. In fact, WorldZone is an Aggregate of the WorldObjects, I seemed to miss out that one.
Why? It has quite big repercussions to say that something is an Aggregate root. For example, if you delete the WZ it has to delete all the WorldObjects. Is that what you want? Or should they just be transferred to another WZ? And whenever you change a WorldObject, do you have any validation rules you need to run on WorldZone? I don't know what you're doing, but from the names it sounds like you're going to have a large amount of WorldObjects, right?
I assume "localIdentitifer" would have to be identity() of the WorldObject. However, finding out which WorldZone WorldObject belongs to, is going to be a little problematic and possibly slow. I am not sure which is going to be more intense - the searching for WorldObject's WorldZone, or the searching for WorldZone's all WorldObjects. I will need to look into that too.
What are your usecases, is the main question. What are the operations you will be performing on these things, and for what purpose.
Yeah, two-way associations seem to be problematic. I think the problem is that expressing one two-way association requires you to do so in two different places, and that just seems to explode all things.
Pretty much. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
