[Nhibernate-commit] nhibernate/src/NHibernate/Property FieldAccessor.cs,1.3,1.4 PropertyAccessorFactory.cs,1.3,1.4

[Michael D. <mik...@us...>]

Update of /cvsroot/nhibernate/nhibernate/src/NHibernate/Property
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8474/src/NHibernate/Property

Modified Files:
	FieldAccessor.cs PropertyAccessorFactory.cs 
Log Message:
Fixing some of the xmldoc problems.

Index: PropertyAccessorFactory.cs
===================================================================
RCS file: /cvsroot/nhibernate/nhibernate/src/NHibernate/Property/PropertyAccessorFactory.cs,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** PropertyAccessorFactory.cs	23 Aug 2004 13:11:08 -0000	1.3
--- PropertyAccessorFactory.cs	10 Sep 2004 21:23:15 -0000	1.4
***************
*** 31,40 ****
  		/// <returns></returns>
  		/// <remarks>
! 		/// <p>
  		/// The built in ways of accessing the values of Properties in your domain class are:
! 		/// </p>
  		/// <list type="table">
  		///		<listheader>
! 		///			<term>access method</term>
  		///			<description>How NHibernate accesses the Mapped Class.</description>
  		///		</listheader>
--- 31,40 ----
  		/// <returns></returns>
  		/// <remarks>
! 		/// <para>
  		/// The built in ways of accessing the values of Properties in your domain class are:
! 		/// </para>
  		/// <list type="table">
  		///		<listheader>
! 		///			<term>Access Method</term>
  		///			<description>How NHibernate accesses the Mapped Class.</description>
  		///		</listheader>
***************
*** 52,56 ****
  		///				in the Mapped Class those will be bypassed and NHibernate will go straight to the
  		///				field.  This is a good option if your setters have business rules attached to them
! 		///				or if you don't want to expose a field through a Getter & Setter.
  		///			</description>
  		///		</item>
--- 52,56 ----
  		///				in the Mapped Class those will be bypassed and NHibernate will go straight to the
  		///				field.  This is a good option if your setters have business rules attached to them
! 		///				or if you don't want to expose a field through a Getter &amp; Setter.
  		///			</description>
  		///		</item>
***************
*** 73,81 ****
  		///		</item>
  		///	</list>
! 		///	<p>
  		///	In order for the <c>nosetter</c> to know the name of the field to access NHibernate needs to know
  		///	what the naming strategy is.  The following naming strategies are built into NHibernate:
! 		///	</p>
  		///	<list type="table">
  		///		<item>
  		///			<term>camelcase</term>
--- 73,85 ----
  		///		</item>
  		///	</list>
! 		///	<para>
  		///	In order for the <c>nosetter</c> to know the name of the field to access NHibernate needs to know
  		///	what the naming strategy is.  The following naming strategies are built into NHibernate:
! 		///	</para>
  		///	<list type="table">
+ 		///		<listheader>
+ 		///			<term>Naming Strategy</term>
+ 		///			<description>How NHibernate converts the value of the <c>name</c> attribute to a field name.</description>
+ 		///		</listheader>
  		///		<item>
  		///			<term>camelcase</term>

Index: FieldAccessor.cs
===================================================================
RCS file: /cvsroot/nhibernate/nhibernate/src/NHibernate/Property/FieldAccessor.cs,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** FieldAccessor.cs	23 Aug 2004 13:11:08 -0000	1.3
--- FieldAccessor.cs	10 Sep 2004 21:23:15 -0000	1.4
***************
*** 67,71 ****
  		/// <returns>The name of the Field.</returns>
  		/// <remarks>
! 		/// This uses the convention that a Property named <c>Id</c> will have a field </c>id</c>
  		/// </remarks>
  		private string GetFieldName(string propertyName) 
--- 67,71 ----
  		/// <returns>The name of the Field.</returns>
  		/// <remarks>
! 		/// This uses the convention that a Property named <c>Id</c> will have a field <c>id</c>
  		/// </remarks>
  		private string GetFieldName(string propertyName)