Try db sequence? You'll find your counter worthless the moment you upgrade your enterprise app to a clustered environment.
Gene --- Alvin Wang <[EMAIL PROTECTED]> wrote: > Hi! Gurus, > > I implemented a synchronized counter (for example Order ID) using Entity > bean and use exclusive concurrency control perperty in WL to ganrantee that > only one transacation is reading/writing that bean at one time point, so > that the generated order id will not duplicate. However, I found it is a > bottleneck. So what is the better design to improve the performance? Or is > there other way to generate non-duplicate ID strings? > > Thanks! > > =========================================================================== > 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". > __________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ =========================================================================== 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".
