checked HibernateException

oneway · **Joined:** Sun Sep 14, 2003 10:54 am **Posts:** 36

gavin wrote:

However, it is VERY easy to write a wrapper for the Hibernate Session that converts exceptions, or to use a fwk like Spring that does this.

Somehow, I see it as follows. The problem is that there are many methods to dispatch, i.e. it's boring. A better way, anyone? Thanks

Code:

import net.sf.hibernate.Session;
import net.sf.hibernate.Transaction;

public class MySessionWrapper {
  private Session hbSession;

  // dispatch ALL hbSession methods as follows
  public Transaction beginTransaction() {
    try {
         return hbSession.beginTransaction();
    } catch (Exception e) {
         throw new RuntimeException("Whatever ...");
    }
    ....
}

emmanuel · **Posted:** Wed Feb 11, 2004 12:41 pm

oneway · **Joined:** Sun Sep 14, 2003 10:54 am **Posts:** 36

emmanuel wrote:

AOP

Am looking for a better solution that DOES NOT involve AOP or Spring. Thanks

emmanuel · **Posted:** Wed Feb 11, 2004 1:28 pm

I know you don't like this idea but changing HibernateException parent class will solve all your problems, it's not that hard to maintain.

oneway · **Joined:** Sun Sep 14, 2003 10:54 am **Posts:** 36

emmanuel wrote:

I know you don't like this idea but changing HibernateException parent class will solve all your problems, it's not that hard to maintain.

Why not make the change for everyone? I think the issue has been brought up often enough to warrant the change.

It appears that all that needed is to change net.sf.hibernate.exception.NestableException to extend the RuntimeException (or its subclass) instead of the Exception. AFAICT, the change should not even break any of the existing code.

emmanuel · **Posted:** Thu Feb 12, 2004 7:07 am

People may have generic code handling RuntimeException and doing different stuffs with it. So it can break old code.