I apologize,
You are right, in terms of entity beans you may
execute more than one call in the same transaction
context (EJB spec, pg 120).
Sorry, was thinking stateless/stateful. I must read
before I type :-)
cheers,
peter
--- Tom Cook <[EMAIL PROTECTED]> wrote:
> On Mon, 19 Feb 2001, you wrote:
> > Hi
> >
> > >
> > > Yep, sounds like deadlock to me. Look for cases
> > > where a client calls a method
> > > on bean A which calls a method on bean B which
> calls
> > > another method on bean A.
> > > Example from a car registration application:
> > >
> >
> > This is a good thought, however, clients are not
> > allowed to make concurrent calls to beans. If an
> > instance of 'A' calls an instance of 'B' and 'B'
> in
> > turns attempts a call to 'A' you will get a
> > java.rmi.RemoteException on 'B'. This is mandated
> by
> > EJB 1.1 and verified in JCTS...
> >
> > Hope this helps.
>
> But I have beans which do this. What is the
> re-entrant flag for if not this?
>
> Tom
>
>
> --
>
--------------------------------------------------------------
> To subscribe:
> [EMAIL PROTECTED]
> To unsubscribe:
> [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35
a year! http://personal.mail.yahoo.com/
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
