-->
These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: Application db persistence design
PostPosted: Thu Jun 23, 2005 7:47 am 
Beginner
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.


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
cron
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.