Ugh, I could not really follow your point about separate transactions.
- If you do not want transactional access to data, what's the point of using EJB's? - This is not a pessimistic transaction with WebLogic & Oracle - A usual design pattern is to wrap handling of a use case behind a session facade which demarcates the transaction. If you mean to separate handling of a use case into different pieces with their own transactions (and forget that you lose ACID qualities of the use case) how would you implement that? Separate methods for each piece (negating the performance benefits of session facade)? Handle transactions inside one method manually by JTA (lose the benefits of automatic transaction handling in EJB)? - - - Janne Mattila Janne Mattila wrote: >Hi, > >isModified could work, have to check that one...separate transactions is a >big no-no. Would mess up transactional integrity. > > What kind of integrity requirement requires you to update all artists and their records in one transaction? Or for that matter, why not put each artist and their records in a single transaction? Even if you solve this deadlock problem, long pessimistic transactions will cause you many more problems. --Victor =========================================================================== 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".
