> It should be legal for two clients to access concurrently
> ServiceClass(session bean).
Illegal. For stateless session beans the two method calls will go to
different instances. For stateful session beans, they will throw an
RMIException.
arkin
> Assuming that it is legal for two clients to access a single ServiceClass,
> how do we enforce
> the critical section within the ServiceClass.
>
> Any ideas?
>
> > Look, your code is not at all suited as an EJB. I would imagine that
> > Complex objects could be *used* by EJB's, but it should not be an EJB by
> > itself.
> >
> > What is the reason you want it as an EJB? What does it solve that it
> > doesn't solve on its own?
> >
> > /Rickard
> >
> > --
> > Rickard �berg
> >
> > @home: +46 13 177937
> > Email: [EMAIL PROTECTED]
> > http://www.dreambean.com
> > Question reality
> >
> >
> ===========================================================================
> > 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".
> >
>
> ===========================================================================
> 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".
===========================================================================
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".
