This should, in general, work. At least there is nothing in the EJB spec that would
say that this is illegal.
Note that the EJB specification does not specify the client environment. Some client
environments may be more restrictive and may choose to restrict the use of the
enterprise bean remote interface.
Vlada
----- Original Message -----
From: Sean C Sullivan <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 26, 1999 5:54 PM
Subject: Creating an EJB, EJBObject.remove, on different threads
> I have a stateful session bean called FooSessionBean
>
> In FooSessionBean's deployment descriptor, I specify a DEFAULT
> access control entry value of [mywebfrontclient]
>
> Now let's say that I have 2 threads: t1 and t2
>
> On thread t1, I create FooSessionBean using FooSessionHome.create
>
> On thread t2, I call FooSessionBean.remove (aka EJBObject.remove)
>
> Should this work?
>
> Are there any restrictions that would prevent thread t2
> from invoking EJBObject.remove?
>
> -Sean
>
> ===========================================================================
> 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".
