commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: [collections] New Collection
Date Fri, 19 Sep 2003 13:10:55 GMT

Howdy,
Attach it an enhancement request in Bugzilla.  And an accompanying test case would be very
nice ;)

Yoav Shapira
Millennium ChemInformatics


>-----Original Message-----
>From: Oxley, David [mailto:David.Oxley@workplace-systems.plc.uk]
>Sent: Friday, September 19, 2003 8:52 AM
>To: 'Jakarta Commons Developers List'
>Subject: RE: [collections] New Collection
>
>Ok. The list won't accept the attachment. If anyone wants to review it, I
>will email it to you directly.
>Dave.
>
>-----Original Message-----
>From: Oxley, David [mailto:David.Oxley@workplace-systems.plc.uk]
>Sent: Friday, September 19, 2003 1:29 PM
>To: 'Jakarta Commons Developers List'
>Subject: RE: [collections] New Collection
>
>Sorry, my patch went missing. Too big? Anyway here it is gzipped.
>Dave
>-----Original Message-----
>From: Oxley, David [mailto:David.Oxley@workplace-systems.plc.uk]
>Sent: Friday, September 19, 2003 1:16 PM
>To: 'commons-dev@jakarta.apache.org'
>Subject: RE: [collections] New Collection
>That's what I meant, cheers.
>I found another collection that seems to be a better starting point,
>org.apache.commons.collections.DoubleOrderedMap. So far I have made a
>couple
>of changes to this class:
>1. Changed it to use Comparator's if specified rather than natural
>ordering.
>
>2. Transaction support.
>I have attached an initial patch. This is NOT for committing as I haven't
>finished yet.
>I have a few questions:
>1. Once I've finished, will the patch be applied (based on what I've
>already
>done)?
>2. Roughly when is the next release of Commons-Collections?
>3. There are no decorators specifically for DoubleOrderedMap. Should I
>write
>some?
>Cheers,
>Dave.
>-----Original Message-----
>From: Arun Thomas <Arun.Thomas@solidusnetworks.com>
>Sent: Fri, 12 Sep 2003 10:19:03 -0700
>To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
>Subject: [collections] New Collection
>Right....
>That seems to be a good interpretation of the original intent.  Should have
>read the original a little better the first time.
>-AMT
>-----Original Message-----
>From: james@carmanconsulting.com [mailto:james@carmanconsulting.com]
>Sent: Friday, September 12, 2003 9:13 AM
>To: commons-dev@jakarta.apache.org
>Subject: Re: [collections] New Collection
>The only problem with SequencedHashMap is that its ordering is based upon
>the insertion order, not the values of the objects added to it or some
>Comparator, such as is needed (at least that's how I interpret "ordering by
>value" from the original requirements).
>----- Original Message -----
>From: "Arun Thomas" <Arun.Thomas@solidusnetworks.com>
>To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
>Sent: Friday, September 12, 2003 12:04 PM
>Subject: RE: [collections] New Collection
>You might want to take a look at
>org.apache.commons.collections.SequencedHashMap which combines, for the
>most
>part, the functions of list and map (insertElementAt()) is not available -
>how does one insert a key, when the value should be at a specific position?
>The transactional support is definitely not there, but this might give you
>a
>better starting point for what you desire.
>-AMT
>-----Original Message-----
>From: Oxley, David [mailto:David.Oxley@workplace-systems.plc.uk]
>Sent: Friday, September 12, 2003 8:07 AM
>To: 'commons-dev@jakarta.apache.org'
>Subject: [collections] New Collection
>Our application has just changed from requiring JDK 1.1 to JDK 1.3 as a
>minimum. As a result we are looking at switching our implementation of
>using
>Hashtable and Vector to using collections.
>I am going to write a new collection that gives the functionality we
>require
>and once I've finished I want to donate it to commons-collections. I would
>like some comments on where to start (especially as I don't yet know too
>much about the standard collections API's). The functionality I require is
>this: 1. Keys and values. ala Hashtable. 2. Ordering by value. ala Vector.
>3. Indexing by value. ala Vector's indexOf, elementAt and insertElementAt.
>4. Transactions. i.e. Others won't see changes until commit is called.
>I take it there is no implementation that supplies the above. I was
>initially thinking of either encapsulating or overriding TreeMap, but I
>think that would make the indexing part pretty difficult. But now I think I
>will just encapsulate or override HashMap.
>Any comments would be gratefully received.
>Cheers.
>Dave.
>david.oxley@workplace-systems.plc.uk
>________________________________________________________________________
>This e-mail has been scanned for all viruses by Star Internet. The service
>is powered by MessageLabs. For more information on a proactive anti-virus
>service working around the clock, around the globe, visit:
>http://www.star.net.uk
>________________________________________________________________________
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
>
>________________________________________________________________________
>This e-mail has been scanned for all viruses by Star Internet. The
>service is powered by MessageLabs. For more information on a proactive
>anti-virus service working around the clock, around the globe, visit:
>http://www.star.net.uk
>________________________________________________________________________



This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


Mime
View raw message