exists() doesn *not* go through the interceptor chain, it will not need to acquire locks etc.
If you want to intercept it, I suggest using JBossAOP and attach an interceptor directly to exists()
exists() does *not* go through the interceptor chain, it will not need to acquire locks etc.
So I'm correct in assuming that the reason exists() doesn't go through the interceptor chain is that the standard interceptors aren't interested in that method call?
What about custom interceptors, though? If you are going to allow people to add their own interceptors, why should these custom interceptors be limited to the methods that the standard interceptors are interested in?
I suggest you to use Aspects, it is quite easy to intercept the call using aspects with out modifiying the original program. I am using a similar approach to implement optimistic locking.
Try JbossCache or others aspect tool as AstectJ.