A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
Java SE 8 for the Really Impatient
this week in the
Joined: Mar 15, 2002
Aug 28, 2003 11:47:00
How does the Transaction should be implemented in a project that don�t use
Is the DAO's responsability to manage the transaction?
Is the DAO methods caller (a "session bean like") responsability?
Joined: Jul 11, 2002
Aug 29, 2003 02:40:00
I would say in this case, you could still have a manager class which deals with some logic surrounding the result set. This manager could manage the connections to the database.
i.e manager->initialise DAO->work with result set... and so on..
Best Regards,<br />Nagendra Prasad.
Joined: Jun 04, 2003
Aug 29, 2003 06:25:00
I'd put the transaction commands (commit, rollback) inside DAO class...
I agree. Here's the link:
one entity bean for entire database
doFilter blocking further request
doubt on use case Change Itinerary
getUserTransaction for SLSB - spec vs HFEJB
WA #1.....word association
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014