Beginner |
|
Joined: Wed Apr 13, 2005 12:49 pm Posts: 34
|
Hi folks,
I've implemented a multi-tabbed swing application. Currently
I'm designing the persistence layer that will take care of any actions that
occur in the swing app.
Each tab represents a single object that needs persisting. I've had a look at
the reference manual regarding transactions and concurrency. They highly
advise not opening and shutting sessions and transactions for every little
amount of work that needs doing. I'm just wondering if anyone has any
suggestions about how I should think about designing the database access as
until now I was implementing that very anti-pattern.
Thanks in advance,
Mark.
|
|