Enthuware

Hi,

The correct answer is:
The bean A instance will be discarded if there is no exception handling code for call to mB().

The explanation is next:
Because the call to mB will throw a javax.ejb.TransactionRequiredLocalException, which extends from EJBException and thus is a system exception. If there is no exception handling for this call, the exception will propagate out of the Bean A instance, which will cause the Bean A instance to be discarded.

As I know if a bean receives RuntimeException(without @application exception) the transaction would be always rolled back (if active) and the bean itself should be discarded.
First time hear that such exceptions could be handled and bean would not be discarded.

Please check.

The explanation is correct. A system exception causes a bean to be discarded when it is not handled i.e. thrown out of the bean to the container. A bean may contain code that causes a runtime exception to be thrown. If the bean doesn't handle it and lets it propagate out to the container, it will be discarded. Otherwise not.

Hi,
Thank you very much for the clear explanation.

Hi all,

I didn't understand why is the answer A wrong...doesn't mA indeed get a javax.transaction.TransactionRequiredException?

Thank you
Regards
Fabio

No, as the explanation says, it will get javax.ejb.EJBTransactionRequiredException.