This week's book giveaway is in the OCMJEA forum.
We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line!
See this thread for details.
The moose likes JDBC and the fly likes Transaction Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "Transaction" Watch "Transaction" New topic
Author

Transaction

Renata fonseca
Ranch Hand

Joined: Mar 15, 2002
Posts: 48
How does the Transaction should be implemented in a project that don�t use EJB?
Is the DAO's responsability to manage the transaction?
Is the DAO methods caller (a "session bean like") responsability?
Nagendra Prasad
Ranch Hand

Joined: Jul 11, 2002
Posts: 219
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.
Willian Corcel
Greenhorn

Joined: Jun 04, 2003
Posts: 13
I'd put the transaction commands (commit, rollback) inside DAO class...
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Transaction