Hi all,

I'm not sure whether I'm going to shot me in the foot with this architecture:

I'm using DAO pattern ( the only class talking to hibernate ) and
thread local session, where I explicitely start transaction
( hibernate ) on retrieving session, anf commit / flush
while giving session back to my session manager.

In case of exception I'm rolling back transaction and close session
on the spot.

While living in swing application, I'm returning session explicitely
and while using my system in web-environment I use filter to flush / close on end of request.

Any objections? Comments?

I don't have any experience with Hibernate + Swing client. However, your web approach looks like the recomended approach for this environment. That is how we handle Sessions in our app server, and we have had zero problems.