At 07:36 PM 24/10/99 +0600, Anton V Antich wrote: >We have posted a patch earlier that addressed this problem. If you like, we >could resend the code. I was having a think about the issue, and I guess the tricky part is that if you have a cascade of beans (in my case a SessionBean calling methods in two other entity beans) and a lower ones causes an error that requires a rollback, then you need to make sure the rolback occurs only in the top most method call. As when you pop out of one of the entity beans with an exception, and the transaction handler goes, "Well, we need to rollback" the question is, does it do it there and then and propigate the exception up the chain, or does it just propigate the exception and then let the top most bean post invoke handle the rollback? If you know what I mean ... -- Subvert the dominant paradigm http://www.cyber4.org/members/grumpy/index.html
