Hemant Khandelwal wrote:
>
> I think it says concurrent calls to the bean class. If concurrent calls are
> made to the SFSB class, does it not imply concurrent calls to the
> corresponding EJBObject ?
>
> Am I missing anything ?
Yes:-)
To expand a little, there are two reasons:
1. The container must serialize incoming calls to bean class instances because
it is pooling them for reuse across bean instances.
2. Simultaneous calls from the same client can validly come to the same bean
instance. Consider this scenario (for SLSB, SFSB or EB):
Client thread 1
o1 = home.create()
handle = getHandle(o1)
start thread 2
use o1
Client thread 2
o2 = handle.getEJBObject()
use o2
Clearly o1.isIdentical(o2), but as o1 and o2 are not the same object there
should be no risk of thread synchronisation errors when o1 and o2 are used
imultaneously. So again the container must synchronise calls to the bean
instance.
I've just realized this is a J2EE issue rather than an EJB issue since it is the
client container (web, applet or app) that is responsible for creating the
client-side objects. Time to peruse the J2EE spec I think!
PS Has anyone got better terms for "bean instance" and "bean class instance"?
I'm for ever falling over these.
========================================
Ian McCallion
Alexis Systems Limited
Romsey, UK
Tel: +44 1794 514883
Fax: +44 1794 501692
========================================
===========================================================================
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".
