Re: [Springframework-developer] DeadlockLoserDataAccessException vs CannotAcquireLockException

[<tho...@tr...>]

I'm OK with PessimisticLockingFailureException as the superclass name.

I wasn't questioning the existence of OptimisticLockingFailureException, I just
can't come up with any SQLException error codes that would translate into it -
it's not a SQL/Database error.  It is definitely thrown by the ORM/DAO code.

I can add this in later today, so we could make 1.2RC1.

Thomas


Quoting Juergen Hoeller <ju...@in...>:

> FYI, we already do throw OptimisticLockingFailureException for Hibernate and
> JDO since the beginning of time :-)
>
> PessimisticLockingFailureException as superclass for
> CannotAcquireLockException and co sounds appropriate to me. Do we want to
> include this in 1.2 RC1, which was originally scheduled for today? ;-) It
> looks like 1.2 RC1 won't be released before Wednesday anyway.
>
> Juergen
>
>
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]On Behalf
> Of Rod Johnson
> Sent: Monday, March 21, 2005 3:00 PM
> To: spr...@li...
> Subject: Re: [Springframework-developer]
> DeadlockLoserDataAccessException vs CannotAcquireLockException
>
>
> Thomas
>
> > ConcurrencyFailureException
> > '- TransactionLockingFailureException [X]
> >     '- CannotAquireLockException [X]
> >     '- CannotSerializeTransactionException [X]
> >     '- DeadlockLoserDataAccessException [X]
> > '- OptimisticLockingFailureException [X?]
> >
> > The [X] indicates that I think we should provide the option for separate
> > categories in sql-error-codes.xml for this exception.  Some of the lower
> > exception classes might not make sense for all databases, but
> > TransactionLockingFailure and OptimisticLockingFailure will provide
> > enough information to retry the transaction if the app developer want to
> > do that.
>
> I like this proposal. Though should it ben
> PessimisticLockingFailureException to match
> OptimisticLockingFailureException? Yes, the latter is intended to be
> thrown by ORM tools, not JDBC-level operations. So we could convert from
> whatever the ORM tool throws. Or developers could throw it themselves,
> still allowing for consistent handling within Spring's DAO abstraction.
>
> R
> >
> > Oracle might have these categories defined:
> >     '- CannotAquireLockException [X]
> >     '- CannotSerializeTransactionException [X]
> >     '- DeadlockLoserDataAccessException [X]
> >
> > while MySQL might have this
> > '- TransactionLockingFailureException [X]
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>