We use a vendor framework that has only a single "gateway" session bean, mostly for remote access purposes. It is actually deployed twice, once as CMT and once as BMT. The gateway dispatches calls to "services" which have to be written to run under CMT or BMT or both. CMT is a very natural fit for most of our services, but we have one that requires BMT and calls existing CMT services via the gateway bean.
Finally the question: Can our call stack go: BMT -> CMT -> BMT ? I don't have handy the details on the symptoms that make us think this is causing trouble. Sorry about that.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
First, it's not possible to propagate your TX context from CMT -> BMT as BMT always starts a new TX. This means that you have to suspend your CMT TX before entering BMT ... (nested TX is not supported ...) So, be careful of the possible behavior.
Second, from BMT -> CMT, if you want to propagate your BMT TX to CMT, you can't set ur CMT TX attr requireNew ...
Overall, this mixed design poses some potential difficulties and should be avoided ...
My 2 cents.
SCJP, SCJD, SCWCD, SCBCD, SCEA, IBM Certified Enterprise Developer, WebSphere Studio V5.0