commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons/collections RELEASE-NOTES-2.0.html
Date Wed, 13 Mar 2002 06:07:14 GMT
mas         02/03/12 22:07:14

  Modified:    collections RELEASE-NOTES-2.0.html
  Update release notes for Bag and BeanMap changes.
  Revision  Changes    Path
  1.5       +43 -5     jakarta-commons/collections/RELEASE-NOTES-2.0.html
  Index: RELEASE-NOTES-2.0.html
  RCS file: /home/cvs/jakarta-commons/collections/RELEASE-NOTES-2.0.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- RELEASE-NOTES-2.0.html	7 Mar 2002 18:24:10 -0000	1.4
  +++ RELEASE-NOTES-2.0.html	13 Mar 2002 06:07:14 -0000	1.5
  @@ -11,8 +11,9 @@
   <p>These collections are new to Collections 2.0:</p>
  -<li><strong>Bag</strong> - A Collection that keeps a count of its members
of the same
  -    type, using <code>hashCode</code> to check for equality. Suppose
  +<li><strong>Bag</strong> - A Collection that counts the number of times
  +    object appears in the collection.  Suppose 
       you have a Bag that contains <code>{a, a, b, c}</code>.  Calling
       getCount on <code>a</code> would return 2, while calling
       uniqueSet would return <code>{a, b, c}</code>.  <i>Note: this is
  @@ -96,7 +97,7 @@
     <li>"Externalized" LRUMap 1.0 Objects cannot be
       read by LRUMap 2.0.</li>
   <p><i>New features:</i></p>
     <li>True LRU algorithm.</li>
  @@ -112,5 +113,42 @@
       when the current size of the Map exceeds the new
       maximum size</li>
  +<p>BeanMap's entrySet() now properly returns a set containing Map.Entry
  +objects.  Previously, entrySet() was equivalent to keySet() (returns a set of
  +the readable properties) and there was no mechanism to retrieve all of the
  +readable properties along with their values.  Additionally, the BeanMap clone
  +method has been revamped to work better for subclasses. </p>
  +<p><i>BeanMap 2.0 compatibility changes:</i></p>
  +  <li>BeanMap's clone() method now declares it throws
  +  CloneNotSupportedException.  This allows subclasses of BeanMap to not require
  +  being Cloneable and facilitates subclasses that wish to be cloneable (allows
  +  the subclass to call super.clone() and have it return an instance of the
  +  child rather than the parent).</li>
  +  <li>If a BeanMap is not cloneable because a new instance of the underlying
  +  bean cannot be constructed, a CloneNotSupportedException is thrown rather
  +  than an UnsupportedOperationException or other RuntimeException.</li>
  +  <li>BeanMap's entrySet() method now returns a set of Map.Entry objects rather
  +  than the set of readable properties.  To retrieve a set of readable
  +  properties, use keySet() instead.</li>
  +<p><i>Bugs fixed:</i></p>
  +  <li>If no bean is set in the BeanMap, or setBean(Object) was called with a
  +  null argument, many BeanMap methods threw NullPointerExceptions.  These have
  +  been fixed to properly handle the case where there is no bean established in
  +  the map.</li>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message