Niclas Hedhman wrote:
On Fri, Apr 3, 2009 at 10:46 AM, Stuart McCulloch <[email protected]> wrote:
extends AbstractAssociation, Iterable<T>
Well, IFF iterator().remove() actually works on the underlying set/list.
That should be ok.
also, the wrapper methods should really be called "asList", "asSet", etc.
because they return views onto the original object (see "Arrays.asList")
rather than copying the contents, while "to..." usually suggests copying
Again, asXyz() only if the intent that calling the Collection's
modifiers will change the underlying association, which *I* think is
not feasible.
IMHO, I think the semantics should be a copy from a managed resource
to a mutilatable JDK collection.
Good point. So keep the toList/toSet, and let them do copies to
ArrayList/LinkedHashSet respectively? Any changes would have to be put
back manually?
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
