I have some doubt about closing session after its use.
I don't wanna have to close the session explicity, because I'm using DAO Design Pattern, so I was thinking in something like this:

What about to close the session in the finalize() method?



This will avoid the problems related to lazy loading, because the session will be closed before garbage collection, and at this time, probably this object is not used anymore.

Is there some problem with this aproach?

Thanks a lot,

finalize can't be relied on.

It will take two garbage collection cycles to collect an object which has a finalize.

Check out Gavin's blog regarding this here:
http://blog.hibernate.org/cgi-bin/blosxom.cgi/2004/02/18/

Have you considered using the "Open Session In View" pattern?

Hi David, thanks for the advice, but, my idea is to make the persistence layer transparent of implementation, for example, now I'm using Hibernate but in the future I could be using another techology, thus, if a use this pattern I'll have Hibernate specific code.

I was thinking about to add a method release() to my AbstractDAO, so all child class will implement it releasing any resource that have been alocated, in case of Hibernate the session and JDBC (for example) the connection.

The Open Session in View pattern DOES NOT create any dependency.

I guess I have to update pattern page (it is quite a mess anyway) to make this clear. Search the forum for discussions about this, here is a recent thread: http://forum.hibernate.org/viewtopic.php?t=927886