Hi

We're trying to integrate Hibernate with the corix 4i Framework (http://www.corix.ch).

4i requires object identity within the live of one JVM process. AFAIK hibernate guarantees object identity only within one session. Thes drives me towards a session-per-application pattern.

Since the wiki entry http://www.hibernate.org/168.html lists this as an anti pattern, I'd like to now what kind of problems I might face.


I already understood the following things:

1. A session is not thread save. If I need thread savety I can maybe wrap the session with a synchronizing dynamic proxy.
2. Getting a HibernateException means, that I've to stop the application. Well not perfect, but I think I shouldn't get HibernateExceptions during normal operation.
3. The session caches every persistent object. This means it grows endlessly. AFAIK Session.clear() isn't an option, since this maybe violates object identity. Would it be possible to patch the session to use weak references for it's cache?

Any ideas are very welcome.
Ernst

I don't think Hibernate is the right choice in this environment. It's completely designed around transaction scoped object idendity.

Ok.

I just like to understand the details: Let's assume I find a way to do a Session.clear() every now and then. Are there other problems with the session-per-application pattern?

TIA
Ernst

You are right about a), b) and c) being a problem in your situation and I don't think your solutions work perfectly. I've never tried something like this myself, so I can't say for sure