Re: [Hibernate-devel] volunteers?

[Gavin_King/Cirrus%<CI...@ci...>]

The trouble with this approach is I think it will make the rest of the
code more prone to bugs if its more difficult to distinguish between a
persistent collection and a view of the persistent collection. And from
a modelling point of view, what the hell do the following methods

     public abstract Iterator entries();
     public abstract Object readFrom(ResultSet rs, CollectionPersister
role) throws Exception;
     public abstract void writeTo(PreparedStatement st, CollectionPersister
role, Object entry, int i) throws Exception;
     public boolean isDirty(java.util.List before, java.util.List after,
Type elementType) throws HibernateException
     public abstract void replaceElements(java.util.Map replacements)
throws HibernateException;

mean for a subset/map?

> I am liking this compromise more and more. I implemented SortedMap
> this way so you'd have a concrete example to evaluate; see cvs. It
> depends on Map.map being non-private, and PeristentCollection read()
> and write() being non-final.