Q. To help you control the overall transaction management process and transaction exception handling.

View solution

Q. You just have to encapsulate your code block in a callback class that implements the TransactionCallback interface and pass it to the TransactionTemplate execute method for execution. In this way, you don’t need to repeat the boilerplate transaction management code for this block.

View solution

Q. A TransactionTemplate can accept a transaction callback object that implements:-

View solution

Q. Spring (since version 2.0) offers a transaction advice that can be easily configured via the:-

View solution

Q. You can omit the transaction-manager attribute in the element if your transaction manager has the name transactionManager.

View solution

Q. A transaction propagation behavior can be specified by the:-

View solution

Q. Transaction propagation behavior are defined in the:-

View solution

Q. If there’s an existing transaction in progress, the current method should run within this transaction.

View solution

Q. The current method must start a new transaction and run within its own transaction.

View solution

Q. If there’s an existing transaction in progress, the current method can run within this transaction.

View solution

Q. The current method should not run within a transaction.

View solution

Q. The current method must run within a transaction.

View solution

Q. The current method should not run within a transaction. If there’s an existing transaction in progress, an exception will be thrown.

View solution

Q. If there’s an existing transaction in progress, the current method should run within the nested transaction.

View solution

Q. For two transactions T1 and T2, T1 reads a field that has been updated by T2 but not yet committed.

View solution

Q. For two transactions T1 and T2, T1 reads a field and then T2 updates the field.

View solution

Q. For two transactions T1 and T2, T1 reads some rows from a table and then T2 inserts new rows into the table.

View solution

Q. For two transactions T1 and T2, they both select a row for update, and based on the state of that row, make an update to it.

View solution

Q. Isolation Levels Supported by Spring:-

View solution

Q. The exceptions that cause a transaction to roll back or not can be specified by attribute:-

View solution