That brings us back to the point that session beans cannot use
synchronization, let me correct that, must not use synchronization, and
one of the drawbacks which GemStone correctly pointed out are deadlocks
and latency.
arkin
> The one solution I have heard that will work is to create a wrapper class around
> the session bean whose methods are synchronized. For each method in the remote
> interface of the bean there will be one synchronized method in the wrapper class
> that will call the remote interface method.
>
> dan
>
> ===========================================================================
> 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".
