[Springnet-commits] Spring.Net/doc/reference/src dao.xml,1.5,1.6

[Mark P. <mar...@us...>]

Update of /cvsroot/springnet/Spring.Net/doc/reference/src
In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv28678

Modified Files:
	dao.xml 
Log Message:
SPRNET-926 - Add PessimisticLockingFailureException as base class for CannotAcquireLockException, CannotSerializeTransactionException, and DeadlockLoserDataAccessException.
SPRNET-927 - NHibernate Exception mapping improvements.
update documentation

Index: dao.xml
===================================================================
RCS file: /cvsroot/springnet/Spring.Net/doc/reference/src/dao.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** dao.xml	23 Jan 2008 03:35:10 -0000	1.5
--- dao.xml	8 Apr 2008 20:26:23 -0000	1.6
***************
*** 105,113 ****
      error codes defined for each data provider in the file dbproviders.xml.
      Refer to this file, an embedded resource in the Spring.Data assembly, for
!     the exact mappings of error codes to Spring DataAccessExceptions. </para>
  
      <para>A common need is to modify the error codes that are map onto the
!     exception hierarchy. There are several ways to accomplish this task.
!     </para>
  
      <para>One approach is to override the error codes that are defined in
--- 105,113 ----
      error codes defined for each data provider in the file dbproviders.xml.
      Refer to this file, an embedded resource in the Spring.Data assembly, for
!     the exact mappings of error codes to Spring DataAccessExceptions.</para>
  
      <para>A common need is to modify the error codes that are map onto the
!     exception hierarchy. There are several ways to accomplish this
!     task.</para>
  
      <para>One approach is to override the error codes that are defined in
***************
*** 151,155 ****
      <literal>dbProviders.xml</literal> have periods in them (i.e.
      SqlServer-2.0 or System.Data.SqlClient). Creating an alias that has no
!     periods in the name is a workaround. </para>
  
      <para>Another way to customize the mappings of error codes to exceptions
--- 151,155 ----
      <literal>dbProviders.xml</literal> have periods in them (i.e.
      SqlServer-2.0 or System.Data.SqlClient). Creating an alias that has no
!     periods in the name is a workaround.</para>
  
      <para>Another way to customize the mappings of error codes to exceptions
***************
*** 178,182 ****
      <para>The ordering of the exception translation processing is as follows.
      The method TranslateException is called first, then the standard exception
!     translation logic, then the FallbackTranslator. </para>
  
      <para>Note that you can use this API directly in your own Spring
--- 178,182 ----
      <para>The ordering of the exception translation processing is as follows.
      The method TranslateException is called first, then the standard exception
!     translation logic, then the FallbackTranslator.</para>
  
      <para>Note that you can use this API directly in your own Spring
***************
*** 236,239 ****
--- 236,282 ----
              example, if we can't connect to a database.</entry>
            </row>
+ 
+           <row>
+             <entry>ConcurrentyFailureException</entry>
+ 
+             <entry>Exception thrown when a concurrency error occurs.
+             OptimisticLockingFailureException and
+             PessimisticLockingFailureException are subclasses. This is a
+             useful exception to catch and to retry the transaction again. See
+             Spring's <link linkend="retry-aspect">Retry Aspect</link> for an
+             AOP based solution.</entry>
+           </row>
+ 
+           <row>
+             <entry>OptimisticLockingFailureException</entry>
+ 
+             <entry>Exception thrown when there an optimistic locking failure
+             occurs. The subclass ObjectOptimisticLockingFailureException can
+             be used to examine the Type and the IDof the object that failed
+             the optimistic locking.</entry>
+           </row>
+ 
+           <row>
+             <entry>PessimisticLockingFailure</entry>
+ 
+             <entry>Exception thrown when a pessimistic locking failure
+             occures. Subclasses of this exception are
+             CannotAcquireLockException, CannotSerializeTransactionException,
+             and DeadlockLoserDataAccessException.</entry>
+           </row>
+ 
+           <row>
+             <entry>CannotAcquireLockException</entry>
+ 
+             <entry>Exception thrown when a lock can not be acquired, for
+             example during an update, i..e a select for update</entry>
+           </row>
+ 
+           <row>
+             <entry>CannotSerializeTransactionException</entry>
+ 
+             <entry>Exception thrown when a transaction can not be
+             serialized.</entry>
+           </row>
          </tbody>
        </tgroup>