Hi ranchers,
I was trying out some features of the
EJB Interceptors and came to a strange behavior:
Statefull session bean defines class interceptor.
Upon calling a method, first is fired the class interceptor, and then the method itself (this is normal).
Console output:
Once I added @PostConstruct to the session bean and to the ClassInterceptor I got the following (normal) behavior:
Now for the weird part: I add a @PostConstruct method in the MethodInterceptor, which is assigned to a *totally* different method from the one being called in the session bean, and I get the following (non-normal?) behavior:
No interceptors are defined in ejb-jar.xml
My Bean code:
ClassInterceptor (MethodInterceptor is identical, just a different .java)
The client:
My question is: why is @PostConstruct on the MethodInterceptor called? It's associated with a method that is not even called at all (demostrated by it's @AroundInvoke method non being called).
Any ideas?
Regards
Alejandro
Edited: forgot to add: using
JBoss 4.0.5
[ June 06, 2007: Message edited by: Alejandro Dominguez ]