Bean provider's responsibilities with exceptions and...transactions
alzamabar
Ranch Hand
Posts: 379
posted 13 years ago
Hi, on HF, page 542, I'm reading the Bean provider's responsibilities for application exceptions. The pages says:
'If you catch an application exception, and find that you can't continue the transaction, call setRollbackOnly() before throwing the exception to the Container.'
At this point I have got a doubt. In the chapter about transaction, I remember that it was clearly stated that only CMT beans with a transaction attribute set to 'Required', 'RequiresNew' and 'Mandatory' should invoke the setRollbackOnly() method, otherwise an exception (it seems to me IllegalStateException but I'm not sure) is thrown. But if the CMT transaction attributes are *NOT* responsibility of the Bean provider, how could the bean provider start from the perspective that the method will have only one of the three required attributes? Doesn't this limit bean's portability (one of the reason why CMT beans will be used most of the time)?
Marco
'If you catch an application exception, and find that you can't continue the transaction, call setRollbackOnly() before throwing the exception to the Container.'
At this point I have got a doubt. In the chapter about transaction, I remember that it was clearly stated that only CMT beans with a transaction attribute set to 'Required', 'RequiresNew' and 'Mandatory' should invoke the setRollbackOnly() method, otherwise an exception (it seems to me IllegalStateException but I'm not sure) is thrown. But if the CMT transaction attributes are *NOT* responsibility of the Bean provider, how could the bean provider start from the perspective that the method will have only one of the three required attributes? Doesn't this limit bean's portability (one of the reason why CMT beans will be used most of the time)?
Marco
Marco Tedone<br />SCJP1.4,SCJP5,SCBCD,SCWCD
Alec Lee
Ranch Hand
Posts: 569
posted 12 years ago
My opinion is that this is fundamental problem of the declarative txn management.
The txn attribute's value definitely affects the program's logic, and the txn attribute may be changed by someone (appli. assembler and deployer) not writing the code (bean provider). That means the program that can be compiled, deployed and running apparently normally will explode occasionally when, say, it needs to rollback something.
Although the spec does allow the Bean provider to supply the recommended value of txn attribute, there is no way to force AA and deployer to follow it!
The txn attribute's value definitely affects the program's logic, and the txn attribute may be changed by someone (appli. assembler and deployer) not writing the code (bean provider). That means the program that can be compiled, deployed and running apparently normally will explode occasionally when, say, it needs to rollback something.
Although the spec does allow the Bean provider to supply the recommended value of txn attribute, there is no way to force AA and deployer to follow it!
