views:

718

answers:

1

I'm using CMT in EJB3 state-less session beans. Also I've created my own Exception having the annotation "@ApplicationException (rollback=true)".

  1. Do I have to use "context.setRollbackOnly()" when I want to rollback the transaction?

  2. Can I just rollback the transaction by throwing an exception inside public method in the bean?

  3. If so (the answer to Q#2 is yes) do I have to throw the exception out of the method by declaring the exception in the method or will it be sufficient to just throw an exception inside the method and handle it inside the same method itself? (I don't want to propagate the exception to the next level. I just want to rollback the exception.)

Thanks in advance. ;)

+1  A: 

First of all, there is no rollback of an exception, it's a rollback of a transaction.

  1. If you throw your exception with @ApplicationException(rollback=true), you don't have to rollback the transaction manually. Context.setRollbackOnly() forces the container to rollback the transaction, also if there is no exception.
  2. An usual checked exception itself doesn't rollback a transaction. It need to have the annotation @ApplicationException(rollback=true). If the exception is a runtime exception and the exception isn't catched, it forces the container to rollback the transaction. But watch out, the container will in this case discard the EJB instance.
  3. As mentioned in 2.), if you throw a runtime exception, the transaction will be rolled back automatically. If you catch an checked exception inside the code, you have to use setRollbackOnly to rollback the transaction.

For further information, check out the free book Mastering EJB. It describes the rollback scenarios very well and is free for download.

Steve
"If you catch an checked exception inside the code, you have to use setRollbackOnly to rollback the transaction."Can you also throw the same exception and rollback the transaction?
ruwan.jayaweera
You can throw the same exception with the throws clause, but the transaction doesn't get rolled back. If you want to rollback the transaction in this case, you have to add the @ApplicationException(rollback=true) to your exception. Another way is to wrap the checked exception inside a unchecked exception (e.g. RuntimeException). But this way is not really preferred, because if a RuntimeException is thrown, the container discards the bean instance and creates a new one.
Steve