Is it a viable solution for a standalone Swing application to have just one session for the whole application ?
If yes, better static or singleton ?

Isn't there any risk that the (single) session gets closed against my will ?

Should I use new 2.1rc1 session.connect() and disconnect() methods ?

Thanks for your attention!

Only 1 user is using your app ?

The session won't be closed, the SQL connection might.

1 user: You might face OutOfMemoryException if you deals with lot's of objects (use session.clear() soemtimes to avoid this)
several users: You might fail into dirty data issues. Session is intended to keep updodate data.

No, many users will use each their own Swing application. Then do you think it's a bad solution ?

I still don't understand if using a single session is a smart choice or not.

Thanks for your attention!

Bad solution.
Keeping the session opened (neither disconnected or closed) implies that your have 1 dB connection for each user. Might be a problem or not, check your DBA.

1 long running session keep data. data become stale when other users play with. => you'll have lot's of concurrent errors (1 user use an old reading of A which has been updated by another).

Try to use session for each 'user transaction', it'll be fine

Ok. Thanks a lot Emmanuel !