In CMT, the complete method is considered to be in a transaction, where as in BMT parts of the method can be in a transaction.
Reducing the scope of a transaction may lead to an increase in performance.
Secondly in a SFSB BMT, the transaction can be kept open across multiple methods. I can't think of any example at the moment to justify the use of BMT, but for most of the practical
J2EE applications, we use CMT.
[ March 11, 2004: Message edited by: Vish Kumar ]