James Cook wrote:
> 1. If multiple containers manage the same bean, it would be improbable to
> implement method synchronization between multiple VMs.
I don't see how that could happen. In a stateless bean you delegate the
method to any server you choose for each method call, so you really
could care less. The same client can make to method calls (serial or
concurrent) one will go to server A, the other to server B, nothing
breaks.
In stateful beans the bean will live in one container for at least the
duration of the method call and certainly for the duration of the
transaction. Moving a stateful bean from one VM to another only works
through passivation and activation, so you know it will never happen
while a method is invoked.
> 2. Some vendors feel that scalability is compromised when the container
> assumes the responsibility of the synchronization source. They feel (and I
> agree) that this is better left to the database to manage.
Right now you cannot do non-synchronized calls anyway, it will throw an
exception. IF the container assumes the role of synchronization it
doesn't replace the database (we're talking about session, not entity),
it simply prevents the pointless RMI exception.
I am not looking at EJB for replacing the database server, on the
contrary, I agree with you that proper transaction synchronization
should occur in the database engine. I am looking at EJB as the TP
monitor on top of the database, in which case EJB should be responsible
for -method- synchronization.
I'm just trying to understand if there is a technical merit to this
design choice, as in, it will break, not work, be hard to implement etc.
arkin
>
> 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".
--
----------------------------------------------------------------------
Assaf Arkin www.exoffice.com
CTO, Exoffice Technologies, Inc. www.exolab.org
===========================================================================
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".
