Hi group, I'd like to effectively do a "select ... for update" SQL query so that other's can't mess around with those rows while I have them. Although this is easy to do, the problem I'm having implementing this with J2EE is dealing with UserTransaction. Specifically, my problems are:
(1) a UserTransaction doesn't "refresh" itself like an HTTP session object does, so it always times out. (2) There is no listener or callback method I can use for user defined transactions that will alert the bean when the transaction has timed out. (3) When the transaction does time out, it's status is changed to marked for rollback but doesn't actually do the rollback. Has anyone else tried to do something like this? Any thoughts on overcoming these issues? Thanks in advance, Mike __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/ =========================================================================== 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".
