----- Original Message -----
From: "Filip Hanik" <[EMAIL PROTECTED]>
> you don't have to lock a stateless session bean since only one client can
> access it (theoretically) at one time :)
Your original statement, "well, consider a clustered server environment where
you will have to keep transactional locks synchronized across servers in a
distributed transaction." refers to the nature of a distributed transaction and
the "weight" it brings to the entity beans involved. I am pointing out that this
distributed transaction and the involvement of XA resources and a transaction
manager will be present even if you use Stateless Session Beans. It is not a
valid argument regarding the weight of Entity Beans. :)
If you are referring to something else, such as synchronized instances of Entity
Beans within a container, this is not the way it works. At least I haven't seen
an EJB container yet that attempts to synchronize EB instances across VMs. As a
matter of fact, WebLogic was the only container that synchronized instances of
Entity Beans *within* its container.
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".
