From: Michael D. <mik...@us...> - 2004-09-10 21:42:51
|
Update of /cvsroot/nhibernate/nhibernate/src/NHibernate/Collection In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8474/src/NHibernate/Collection Modified Files: PersistentCollection.cs Set.cs Log Message: Fixing some of the xmldoc problems. Index: PersistentCollection.cs =================================================================== RCS file: /cvsroot/nhibernate/nhibernate/src/NHibernate/Collection/PersistentCollection.cs,v retrieving revision 1.13 retrieving revision 1.14 diff -C2 -d -r1.13 -r1.14 *** PersistentCollection.cs 2 Sep 2004 15:07:19 -0000 1.13 --- PersistentCollection.cs 10 Sep 2004 21:23:14 -0000 1.14 *************** *** 14,19 **** /// persistent when held by a persistent object. Collections can be /// passed between different objects (change "roles") and this might ! /// cause their elements to move from one database table to another.<br> ! /// <br> /// Hibernate "wraps" a java collection in an instance of /// PersistentCollection. This mechanism is designed to support --- 14,19 ---- /// persistent when held by a persistent object. Collections can be /// passed between different objects (change "roles") and this might ! /// cause their elements to move from one database table to another. ! /// <br /><br /> /// Hibernate "wraps" a java collection in an instance of /// PersistentCollection. This mechanism is designed to support *************** *** 21,30 **** /// lazy instantiation of collection elements. The downside is that /// only certain abstract collection types are supported and any ! /// extra semantics are lost<br> ! /// <br> ! /// Applications should <em>never</em> use classes in this package ! /// directly, unless extending the "framework" here.<br> ! /// <br> ! /// Changes to <em>structure</em> of the collection are recorded by the /// collection calling back to the session. Changes to mutable /// elements (ie. composite elements) are discovered by cloning their --- 21,30 ---- /// lazy instantiation of collection elements. The downside is that /// only certain abstract collection types are supported and any ! /// extra semantics are lost. ! /// <br /><br /> ! /// Applications should <b>never</b> use classes in this package ! /// directly, unless extending the "framework" here. ! /// <br /><br /> ! /// Changes to <b>structure</b> of the collection are recorded by the /// collection calling back to the session. Changes to mutable /// elements (ie. composite elements) are discovered by cloning their *************** *** 32,36 **** /// time. /// - /// @author Gavin King /// </summary> [Serializable] --- 32,35 ---- Index: Set.cs =================================================================== RCS file: /cvsroot/nhibernate/nhibernate/src/NHibernate/Collection/Set.cs,v retrieving revision 1.12 retrieving revision 1.13 diff -C2 -d -r1.12 -r1.13 *** Set.cs 2 Sep 2004 15:07:19 -0000 1.12 --- Set.cs 10 Sep 2004 21:23:14 -0000 1.13 *************** *** 32,36 **** /// <summary> ! /// Returns a Hashtable where the Key & the Value are both a Copy of the /// same object. /// <see cref="PersistentCollection.Snapshot"/> --- 32,36 ---- /// <summary> ! /// Returns a Hashtable where the Key & the Value are both a Copy of the /// same object. /// <see cref="PersistentCollection.Snapshot"/> |