You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Matt Benson (JIRA)" <ji...@apache.org> on 2007/08/30 18:06:30 UTC

[jira] Closed: (COMMONSSITE-18) Project Proposal: Persistent Collections Framework

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

Matt Benson closed COMMONSSITE-18.
----------------------------------

    Resolution: Invalid

With regard to creating new commons components, I'd say you were misinformed when a list member suggested you enter these as JIRA issues. Please see: http://commons.apache.org/oldcharter.html for a rough idea of the process by which a new component could be started in Commons (by somone who is not already an ASF committer).

> Project Proposal: Persistent Collections Framework
> --------------------------------------------------
>
>                 Key: COMMONSSITE-18
>                 URL: https://issues.apache.org/jira/browse/COMMONSSITE-18
>             Project: Commons All
>          Issue Type: New Feature
>         Environment: Java 5.0 and higher, all platforms
>            Reporter: Matt Rothe
>
> The proposed Persistent Collections Framework aims at creating a collections framework that seamlessly integrates with the JCF (Java Collections Framework) while permitting transparent persistence.
> Say you've got an ArrayList (or some other collection or map type) of data objects you need to work with and store away. Usually you would have to load the objects from some source (XML, database etc.) put them into the ArrayList to manipulate or use them and later store any changes to them yourself.
> I think this can be done more transparently by telling the ArrayList were to get its objects, work on those objects and let the ArrayList handle all the persistence issues. That would make working with persistent objects as simple as working with in memory ones.
> By using a strategy pattern any kind of data source could be wrapped and therefore become accessible for any collection or map type.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.