commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons/collections DEVELOPERS-GUIDE.html
Date Sat, 29 Jun 2002 03:49:02 GMT
mas         2002/06/28 20:49:02

  Added:       collections DEVELOPERS-GUIDE.html
  Formalize naming conventions proposal.
  Submitted by: Stephen Colebourne
  I made a few minor modifications (e.g. adding </li> tags), along with modifying
  the requirement of static inner classes for the decorators to be more in line
  with my perception of consensus from the discussion.
  Revision  Changes    Path
  1.1                  jakarta-commons/collections/DEVELOPERS-GUIDE.html
  <title>Developers guide for Jakarta Commons "Collections" Package</title>
  <body bgcolor="white">
  <div align="center">
  <h1>The Jakarta Commons <em>Collections</em> Package</h1>
  <h2>Developers Guide</h2>
  $Id: DEVELOPERS-GUIDE.html,v 1.1 2002/06/29 03:49:01 mas Exp $<br>
  <a href="#Introduction">[Introduction]</a>
  <a href="#CollectionInterfaces">[Collection Interfaces]</a>
  <a href="#CollectionImplementations">[Collection Implementations]</a>
  <a href="#UtilityClasses">[Utility Classes]</a>
  <a name="Introduction"></a>
  <h3>1.  INTRODUCTION</h3>
  <p>The <em>Collections</em> package contains a set of Java classes that
  or augment the Java Collections Framework. This developers guide seeks to set
  out rules for the naming of classes and methods within the package. The purpose
  of this, as with all naming standards, is to improve the coherency and
  consistency of the whole API.</p>
  <p>The philosophy of the naming standards is to follow those of
  <a name="CollectionInterfaces"></a>
  <p>Collection interfaces are new types of collections not included in Java.
  Examples include <code>Bag</code> and <code>SortedBag</code>. These
  <li>be top level interfaces</li>
  <li>have a name that describes their purpose</li>
  <a name="CollectionImplementations"></a>
  <p>Collection implementation are new implementations of collection interfaces.
  Examples include <code>DoubleOrderedMap</code> and <code>DefaultMapBag</code>.
  These interfaces shall:</p>
  <li>be top level classes</li>
  <li>have a name that ends with the collection type being implemented</li>
  <li>have a name that describes their implementation</li>
  <li>contain no public inner classes</li>
  <li>only contain the collection implementation, and any methods specific to
  that implementation</li>
  <a name="UtilityClasses"></a>
  <h3>4.  UTILITY CLASSES</h3>
  <p>Utility classes provide additional functionality around an interface and
  its basic implementations. Examples include CollectionUtils and ListUtils.</p>
  <p>Each class shall follow the naming pattern XxxUtils where Xxx relates to the
  object being returned by the class, for example <code>ListUtils</code> and
  <code>BagUtils</code>. Variations on a theme (<code>SortedBag</code>
as opposed
  to <code>Bag</code>) will be dealt with in one Utils class. Each Utils class
  <li>be a single, static method based, class</li>
  <li>have a name consisting of the interface name plus 'Utils'</li>
  <li>deal with one collection interface and its variations</li>
  <li>provide methods that decorate the interface with additional
  <li>provide methods that perform useful utility functions on that
  <p>Where the method in a Utils class is a decorator, the naming pattern
  yyyedXxx shall be used, such as <code>synchronizedMap(Map)</code> or
  <code>predicatedSet(Set)</code>.  Typically, these decorators should be
  implemented as non-public, static, inner classes; however, if warranted due to
  maintenance or other reasons, these decorator classes may be moved to top-level
  classes in a subpackage.  The naming of such a subpackage should be discussed
  and agreed upon on the developers mailing list.</p>

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

View raw message