Enthuware

the explanation that you gave for first option(for onMessage) cant that explanation apply to lifecycle callback interceptor methods ?? why ?

Seems like we can throw application exception from life cycle callback interceptors also the same way thrown by onMessage method.

Option 1 is talking about MDB while option 3 is talking about all the beans in general. As per section 12.5.1 :

Lifecycle callback interceptor methods may throw system runtime exceptions, but not application exceptions.

HTH,
Paul.

public class MyEx extends IOException{}

Is MyEx is application exception?

Or is it always necessary to annotate it with @ApplicationException to make it application exception?

In your example MyEx is an application exception. @ApplicationException is not required if the exception is a checked exception.

HTH,
Paul.

Thanks a lot Paul

Since "Session bean business method is allowed to throw system exception." was not a valid answer, I think the option can be amended to "Session bean business method is allowed to [only] throw system exception."

Amaebi, it is a valid answer.

Hello ,

In the second option "Business method interceptor methods may throw runtime exceptions ......"

What this option mean here by business method interceptor methods , please give an example.

You can specify interceptor classes for business methods of a bean. It is talking about methods of those interceptor classes. Please see section 4.3.13 of EJB 3.1 specification for details.

HTH,
Paul.

The explanation to option 4 should mention that in case the business method throws a system exception the bean instance is discarded (if it is not a Singelton).