--Original Message-
> From: Emmanuel Bernard [mailto:[EMAIL PROTECTED]
> Sent: Sunday, January 23, 2005 4:03 PM
> To: [EMAIL PROTECTED]
> Cc: hibernate-devel@lists.sourceforge.net
> Subject: Re: [Hibernate] HibernateException now a RuntimeException
>
> Hi Scott,
> Actually we
Hi Scott,
Actually we kinda think the opposite :-) and we're not alone (see the
Spring exception wrapper for example).
We consider checked exceptions as receverable contractual issues.
HibernateException have to be treated as not recoverable and the Tx has
to be rollbacked. As stated by the EJB s
On Jan 24, 2005, at 12:45 AM, <[EMAIL PROTECTED]> wrote:
I searched the mailing list and I couldn’t find the reason for why the
HibernateException was changed to a RuntimeException. If a failure
occurs while persisting an object, for example if the database becomes
unavailable, it would seem th
I searched the mailing list and I couldn’t find the
reason for why the HibernateException was changed to a RuntimeException. If a failure occurs while persisting an object, for example if the database becomes
unavailable, it would seem that the client should be forced to handle the
failure
