This is nothing new. In the database world, we've had to deal with different behaviours depending on the DBMS being used and consequently error-handling code was always DBMS dependant. Rolling back or blocking depends on how the DBMS implements concurrency/isolation. If we want true portability in the ejb world, then the container must handle the rollback case. Of course, as someone pointed out, a re-try may not always be the correct solution, in which case this needs to become a DD property. Shanti > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > X-Priority: 3 (Normal) > X-MSMail-Priority: Normal > Importance: Normal > X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 > From: Floyd Marinescu <[EMAIL PROTECTED]> > Subject: Re: Serializable was: can multiple instances of an entity bean... > To: [EMAIL PROTECTED] > > Thanks for your help Victor, see below. > > > >It depends on the app server and database you're using. If locking isn't > used, > >one transaction may rollback instead of blocking. > > It occurs to me that this behavior is extremely important, and is > something that should be specified somewhere. How could one transaction > either block or rollback? As a developer trying to write portable code, it > is scary that I can't assume consistent behaviour on such a fundamental > issue to transaction processing as how to deal with serializeable > transactions. Maybe BEA made the right choice, I think it is much easier on > the developer's side of things if a transaction blocks, rather than rolls > back (and all the error handling required for this case). > > Floyd > > =========================================================================== > 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".
