Nice. I'm doing something very similar (reading in declared exceptions,
logging if not declared). Thanks for the reinforcement. :)
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4005908#4005908
Reply to the post :
http://www.jboss.com/index.html?mod
For me it looks like this:
| package fr.toto.interceptor;
|
| import java.lang.reflect.Method;
| import java.lang.reflect.UndeclaredThrowableException;
| import java.util.logging.Level;
| import java.util.logging.Logger;
|
| import org.jboss.aop.advice.Interceptor;
| import org
I've made a little Interceptor to do the trick here, but when configuring, I'm
unsure how to signal to AOP that I'd like to intercept "all client calls to the
service methods", not "all calls to service methods, including internal ones
when a service method calls another".
I've currently config
anonymous wrote : Always wondered why unchecked/undeclared exceptions get
wrapped...
Will correct myself. I understand why they're wrapped. I do not understand
why they are not thrown on the server to generate an error.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module
Wow, great. Looks like the interceptor-based solution will be the way to go.
Will try this out and repost. Thanks.
Always wondered why unchecked/undeclared exceptions get wrapped...
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999011#3999011
Rep
I don't know if it is the best solution but for catching exception I have added
an interceptor in ejb3-interceptor.xml. This interceptor is set for remote
session bean.
In my case, interceptor catch exception, logg it on server side and throw a new
exception without all the chained exception b
