2013/2/12 Roger Kratz <[email protected]>: > · In some thread, which I can’t find at the moment, I got the > impression that NH should drop support for all its non-generic collections > in v4?
It's still planned for 4.0. https://nhibernate.jira.com/browse/NH-3345 > · (Too late) I’ve seen there’s been discussions on this list how to > handle OrderedSet when going for BCL’s ISet. FWIW, I think you should drop > Iesi.Collections all together from Nh Core. My guess is that users using > OrderedSet are quite few and for users using it, there are great extension > points in NH to do this on their own (or let the community build a 3rd party > lib for this). > I vote for simply drop orderedset support from DefaultCollectionTypeFactory > to get rid of Iesi.Collection dependency all together. But I guess this > decision is already made? I don't think this idea was discussed and rejected. The use for Iesi 4.0 in NH is really narrow, so it's tempting to remove it. One complication is that the mapping syntax has the "ordered" attribute. What should we do if the developer specifies this for a set-collection (to follow the principle of "easy to get it right, hard to get it wrong")? I suppose we can refuse to accept such a mapping unless the user has also specified a custom collection type? Then we could package an "official contrib" with the Iesi integration. /Oskar -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
