For client- or bean-managed transactions, the beginning and ending are
explicit. For the declarative transaction management types, the container
typically embeds calls to begin() and commit() in the generated wrapper
code. If you're using Tengah, try running ejbc with the -keepgenerated
option and peruse some of the code.
So there's no real magic involved -- the transaction is over when the
method returns; the wrapper then calls commit() and does its own return.
On Tue, 15 Jun 1999, James Cook wrote:
> Probably a strange question, but how do transactions in EJB know when the
> transaction is over. I am assuming that when a call is invoked from a client
> or from a bean, the thread context must determine the starting and ending
> points of the transaction. Is this the case?
>
> jim
============================================================================
Tom Valesky -- [EMAIL PROTECTED] -- http://www.patriot.net/users/tvalesky
"Enterprise JavaBeans: Developing Component-Based Distributed Applications"
http://cseng.aw.com/bookdetail.qry?ISBN=0-201-60446-9&ptype=0
===========================================================================
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".
