dlr         01/08/24 12:11:46

  Modified:    util/src/java/org/apache/commons/util
                        SequencedHashtable.java
  Log:
  Cleaned up JavaDoc.
  
  Revision  Changes    Path
  1.3       +11 -8     
jakarta-commons-sandbox/util/src/java/org/apache/commons/util/SequencedHashtable.java
  
  Index: SequencedHashtable.java
  ===================================================================
  RCS file: 
/home/cvs/jakarta-commons-sandbox/util/src/java/org/apache/commons/util/SequencedHashtable.java,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -u -r1.2 -r1.3
  --- SequencedHashtable.java   2001/08/08 23:56:48     1.2
  +++ SequencedHashtable.java   2001/08/24 19:11:46     1.3
  @@ -63,23 +63,26 @@
   import java.util.Set;
   
   /**
  - * A {@link java.util.Hashtable} whose keys are sequenced.  The
  + * <p>A {@link java.util.Hashtable} whose keys are sequenced.  The
    * sequencing of the keys allow easy access to the values in the order
  - * which they were added in.  This class is thread safe.
  - * <p>
  - * Implementing the List interface is not possible due to a instance
  + * which they were added in.  This class is thread safe.</p>
  + *
  + * <p>Implementing the List interface is not possible due to a instance
    * method name clash between the Collection and the List interface:
    *
    * <table>
    * <tr><td>Collections</td><td>boolean remove(Object o)</td></tr>
    * <tr><td>Lists</td><td>Object remove(Object o)</td></tr>
    * </table>
  + * </p>
    *
  - * So one cannot implement both interfaces at the same, which is unfortunate
  - * because the List interface would be very nice in conjuction with Velocity.
  + * <p>So one cannot implement both interfaces at the same, which is
  + * unfortunate because the List interface would be very nice in
  + * conjuction with <a
  + * href="http://jakarta.apache.org/velocity/";>Velocity</a>.</p>
    *
  - * A slightly more complex implementation and interface could involve
  - * the use of a list of <code>Map.Entry</code> objects.
  + * <p>A slightly more complex implementation and interface could involve
  + * the use of a list of <code>Map.Entry</code> objects.</p>
    *
    * @author <a href="mailto:[EMAIL PROTECTED]";>Daniel Rall</a>
    * @author <a href="mailto:[EMAIL PROTECTED]";>Henning P. Schmiedehausen</a>
  
  
  

Reply via email to