Hi.
I have a BMT SFSB, call it SFBean, that starts a transaction in method
a() and then calls a method on a CMT SLSB, call it SLBean.a().
SFBean.a() returns without completing the transaction. The client then
calls SLBean.b(), which is marked as Required, and JBoss complains that
there is already a transaction active and it can't nest the new one.
1. Client calls SFBean.a()
2. SFBean.a() starts a transaction
3. SFBean.a() calls SLBean.a()
4. SLBean.a() returns
5. SFBean.a() returns
6. Client calls SLBean.b() - JBoss says there is already a transaction
If I change SLBean.b() to be Supports, then I can see (by printing
TxManager.getTransaction()) that it is invoked in the context of the
transaction started by SFBean.a(). So, it looks as though the instance
of SLBean is being associated with the transaction.
I thought this was only meant to happen (associating a transaction with
an instance) for BMT stateful session beans. Am I missing something in
my reading of the spec or is this is bug in JBoss?
Toby.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
