Throwing exceptions from EJB interceptors?

Here are a couple of things to try: 1. Check that the authorize(...) method is called. 2.

Try making the authorize(...) method public instead of private. 3. Check that the EJB has an annotation like this: @Interceptors(AuthorizationInterceptor.

Class).

1. The method is indeed called - I can see the log message executing; Number 2 & 3 are also checked. Thanks anyway – Bogdan Dec 7 '10 at 12:12.

After searching a bit for this issue, I found this SO post which was answered a few minutes ago. Quote: 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.

Question author is the same person who answered and accepted this answer, so I guess he was trying to solve the same issue as you and came to conclusion that it cannot be done.

Darioo, thanks for taking the time to research this. I'm not experiencing the same issues as this user; after I corrected my problem client-side, the interceptor throws exactly the defined exception, so everything is fine, for now :) – Bogdan Dec 7 '10 at 17:20.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.