When you choose to demarcate the transaction via a stateless session bean method call, in order to reduce network calls, what concurrency guarantees does the container make? There's nothing stopping a situation where two threads each are mid remote call on the same method touching the same entity beans right? So, are you still on your own WRT to managing concurrency with this pattern? ie. you still have to implement your own optomistic or pessimistic locking strategy? What implicit synchronisation takes place here? If any? I assume none because you cannot assume how many session beans nor entity bean instances will be handling this request. =========================================================================== 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".
