On 27 May 00, at 17:51, Aaron Mulder wrote:
> On Sat, 27 May 2000, marc fleury wrote:
> > There is always "how did we do it in jBoss 1.0" to help us ...
> >
> > ok the session bean can see the transaction through the JTA interfaces. A
> > bean can perfectly start a transaction in BMT mode. (Bean Managed Tx,
> > personal lingo)
>
> I agree that a session bean can start a transaction manually when
> in BMT. My question is whether one should be created automatically while
> in "CMT" mode. I thought all bean method invocations would have a new
> transaction generated by the container. But when I set my (stateless
Hi Aaron,
This depends on the transaction attributes set for the EJB's
methods in the deployment descriptor. You should look at chapter
11 in the EJB 1.1 spec. Basically, there are six transaction
attributes that need to be combined with the "existing transaction"
and "no existing transaction" cases to come up with all the
possibilities about whether a transaction should be created
automatically, an existing transaction should be used, an existing
transaction should be suspended, a method should execute in an
"unspecified transaction context," or an exception should be
thrown.
-Dan
> session) bean for CMT mode, there's no transaction - assuming I'm okay
> with one global transaction manager, which seemed to be the gist of the
> rest of your message. So I wonder whether my understanding is wrong or
> whether I'm reporting a bug.
>
> Aaron
>
>
