On 17 July 2013 11:40, GESCONSULTOR - Óscar Bou <[email protected]>wrote:
> > > Instead of modifying each Domain Entity, perhaps some reflection "hack" on > the unit tests? I don't know the internals, not sure how this could be > achieved and the effort required. If not possible, I would prefer to add > those conditions to the tests. > Hmm, I can't see a way to do this, I'm afraid. There is no interception layer to exploit if the collection is being modified directly by an action. > > > Regarding "duplication" of the same object on a DN Set under some > circumstances, the SortedSet is descending from Set, so it's curious... I > don't know DN implementation internals neither, but, could it be a problem > with equalTo, compare, etc contracts? It's just so strange... > Yeah, that's what I thought. But in fact, its not that there are two objects that are equal in the set, it is that the SAME object instance is in the set twice. > > > All tests by now seem to work ok with just DN annotations, managing DN all > bidir relationships. That's good to hear. Always nice to delete code, isn't it. > There are still some pending (we have migrated to the latest Isis > snapshot). If anything changes, I will properly inform. > > OK, let me know. Dan > >
