Hi,

I'd like some advice on handling session.iterate().

So far my hibernate usage pattern for storing/loading object has been: open session->load/save->close session->return to business layer. Now, I'm adding support for loading large lists of records using session iterate and this usage breaks down as I cannot close the session until after I am done iterating through the result set.

Here's my question. Given that I don't what the business logic layer to know anything about the underlying persistence layer (except the fact that it exists), how do I make sure the session gets closed after I'm done using the iterator?


Thanks
Dmitry

AOP and interception points on your business boundaries.
Interceptor implements Thread local Session pattern (see the wiki)

I may not have worded my question correctly (or I misunderstood the reply). What I meant to ask was: what's the best way to close the session after the business layer is done using the iterator, assuming that I don't want the business layer to know about the session's existance.

http://www.hibernate.org/43.html

Can you use this pattern? (you don't need to do exactly what's in the example, if you aren't using servlets you can still use a ThreadLocal in something else that gets called before and after your business layer)

If you'd use the Spring Framework's transaction management, the Hibernate Session would get closed after transaction commit, through automatic transaction synchronization. This works with both HibernateTransactionManager and JtaTransactionManager.

Your business layer would just know about generic transaction demarcation, or not even about that when using declarative demaration via AOP, but not about any details of the persistence layer.

Juergen

thanks guys!!! David, that link was great. It helped me finally understand what Emmanual meant by his reply.