This week's book giveaway is in the Cloud/Virtualization forum. We're giving away four copies of Mastering Corda: Blockchain for Java Developers and have Jamiel Sheikh on-line! See this thread for details.
If a local client in a transaction context invokes a business method on a bean with container-managed transactions, what exception does the client receive if the bean instance throws a non-application exception?
The answer is javax.ejb.TransactionRolledbackLocalException, why is it not javax.ejb.EJBException?
This really confuses me
When the transaction is rolled back by CONTAINER in the result of system exception, and a client try to commit the transaction, transactionRolledback(Local)Exception will thrown.
When the transaction is marked rollback only by bean, and a client try to commit the transaction, the TransactionRolledback(Local)Exception will NOT thrown.
Am I right ? Why is TransactionRolledback(Local)Exception thrown in the above situation?
After I review Val's cheap sheet on exception, I realize this has something to do with if the tx is started by the caller or not. If the exception occurs in the same tx context as the caller, the TransactionRolled(Local)backException will be thrown, otherwise client will receive either EJBException or RemoteException.
Oh another thing I like to clear out, just for my own benefit, is that bean provider can't never throw RemoteException, it should be always wrapped as an EJBException. The remote client will receive RemoteException, local client will receive EJBException.
SCBCD, SCWCD, SCJP
All of the following truths are shameless lies. But what about this tiny ad: