Ian,
You're right. The example you point to is a session bean which manages a transaction
over other bean method calls and more than one client method call. While I didn't
explicitly state this, my definition of ejb client is any code that calls an
enterprise java bean. That includes other enterprise java beans, corba objects,
etc... In which case you're example is really #2. But certainly that is not obvious.
Thanks,
Victor
Ian McCallion wrote:
> Victor Langelo wrote:
> >
> > You have too options:
> >
> > 1. Create a session bean method that preforms the entire transaction by calling
> > other bean methods.
> > 2. Have the ejb client manage the transaction using the UserTransaction object.
> >
> > --Victor
>
> I don't think this is true. It is perfectly possible to have a transaction that
> the client knows nothing about spanning multiple transactions. See pages 164 and
> 165 of the EJB 1.1 spec for an example.
>
> Ian McCallion
> Alexis Systems Limited
> Romsey, UK
>
===========================================================================
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".
