You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Thomas Neidhart (JIRA)" <ji...@apache.org> on 2015/05/24 13:09:17 UTC

[jira] [Resolved] (COLLECTIONS-248) TrackingCollection

     [ https://issues.apache.org/jira/browse/COLLECTIONS-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Neidhart resolved COLLECTIONS-248.
-----------------------------------------
       Resolution: Won't Fix
    Fix Version/s:     (was: 4.x)

This issue has been open for several years and there was no further interest, thus closing as Wont'Fix for now.

> TrackingCollection
> ------------------
>
>                 Key: COLLECTIONS-248
>                 URL: https://issues.apache.org/jira/browse/COLLECTIONS-248
>             Project: Commons Collections
>          Issue Type: New Feature
>          Components: Collection
>            Reporter: Nicolas Marchildon
>         Attachments: CollectionLoader.java, TrackingCollection.java, TrackingCollectionTest.java
>
>
> Sometimes you need to keep track of what was added and what was removed
> from a collection, and that is what we created TrackingCollection for.
> Additionally, since we were implementing lazy-loading of collections of
> persistent objects, we introduced a CollectionLoader that is used by the
> TrackingCollection when it has to access all of its elements. It is
> still possible however to use the TrackingCollection without a loader,
> and it will simply start empty and be considered loaded.
>     Sherpa Solutions is offering the Apache Software Foundation the
>     attached source code, to be distributed by the projet under the
>     Apache License terms.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)