You might consider implementing some type of optimistic/pessimistic locking mechanism using a time stamp from the DB. It gets tricky because if you start locking stuff you need to guarantee that you can unlock it after a time out period say; maybe with a timer thread. Also, check out the Version Pattern in the EJB Design Patterns book by Floyd Marinescu. Although it relates to entity beans you may be able to apply something similar.
Good Luck. Anthony Catalfano Information Technology Analyst Deere & Company 309-748-5201 -----Original Message----- From: Neelu Mehta [mailto:nmehta@;MTCINDIA.COM] Sent: Wednesday, October 23, 2002 1:10 PM To: [EMAIL PROTECTED] Subject: dirty reads from database Hi All I'm using Oracle Application Server9I . In our application we've session beans and Database Access Objects(DAO). We don't have Entity Beans at all. I want to know that How it works in multi user environment. Just like CMP or BMP can we set any attributes for DAOs like Roll back functionality How can we avoid Dirty reads Performance Can anyone suggest me any link or any book for that.. Thanks in advance Neelu Mehta =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help". =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
