CODEWITHSUNDEEP
javaejb-3.0interceptor
Gnoupi
Gnoupi

Reputation: 4734

What is the proper way to deal with Exceptions in Interceptors in EJB3?

I want to use an interceptor for my bean, which will check the validity of a given connection token.

If the connection is invalid, I want to throw a particular exception, if the connection expired, I want to send another (TokenExpiredException, something like this). These Exceptions are included in the interface given to the client.

@AroundInvoke
public Object checkParams(InvocationContext ctx) throws TokenExpiredException, Exception{
    //code to check token
    //...
    throw new TokenExpiredException(); 
}

From what I tried, throwing such specific Exception in the Interceptor leads to an UndeclaredThrowableException on the client side. While this exception includes the reference to the cause, it is not really ideal, and can't be dealt with with regular catch clauses.

What is the correct way then to declare different Exception types with Interceptors?

Upvotes: 1

Views: 780

Answers (1)

Gnoupi
Gnoupi

Reputation: 4734

I don't think there is a correct way to do that. Methods should throw only the exceptions they declared, and an interceptor shouldn't add a new one.

My personal case got fixed by adding an error code to our default exception which is thrown by all methods.

Upvotes: 1

Related Questions