> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Francis Pouatcha
> 1. I'm speaking about writting portable bean. I can't presume optimistic
> or pessimistic locking when writting a bean.
If you want a portable bean, and this bean will run on a domain that is
outside your control (3rd party, customer), then I believe that you have to
assume optimistic locking. This is due to the way that concurrency must be
handled in a clustered environment.
I think the WebLogic approach of pessimistic (single container) *and*
optimistic (clustered) would drive most developers nutty if they counted on
some kind of EJB container locking to support concurrency.
Concurrency can only be achieved at one location. No matter how many
creative solutions and layers we have added to the problem, every system
always will have one bottleneck. There is nothing wrong with this either. In
fact, it is necessary, because this is the only place that concurrency can
be truly supported. For most of us developing EJB's, concurrency is a
developer responsibility and it is facilitated by the database. In
multi-database scenarios, the TX manager is the "bottleneck".
jim
===========================================================================
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".
