Hi everyone,

i'm facing a big issue in the use of Spring.
For some reason, there's a query I need that can't be fetched into persistent objects.
I can't avoid to return a ScrollableResults.
Since getHibernateTemplate() doesn't provide any methods able to return a ScrollableResults I'm kind of stuck there.

Would applying AOP Interceptor a solution to my pb?

In such cases, implement a HibernateCallback, and execute it with HibernateTemplate's generic execute method. You can do anything you like with the Hibernate Session there, still properly participating in Spring's resource and transaction management. You do not need to close the Session in a finally block or the like: HibernateTemplate will do this for you.



Juergen

All right, that's really helpful!!

but i did implement an AOP interceptor by that time, which is really nice I must say.

So what's the big avantage of AOP interceptor over hibernate template except being able to throw checked exception?

HibernateTemplate and HibernateInterceptor basically offer the same level of resource management, just in a different style. HibernateInterceptor's main advantage is indeed that your data access code can throw any checked exceptions.

Juergen

And performance wise, are interceptors slowing down during the runtime in any manner?
Or can you neglect that?
Or is it even faster?

(Sorry it might be a stupid question but i'm really new to AOP)

If you register the interceptor for a target that doesn't need to be proxied otherwise, it will slow down invocations to some degree. But this is neglectable for non-trivial methods: Consider all the work that your data access operation initiates, going through Hibernate and your JDBC driver...

As it doesn't involve proxy setup and offers a lot of convenience methods, I recommend to use HibernateTemplate: With custom HibernateCallback implementations, you should be able to cover any sort of data access operation on a Hibernate Session.

Juergen