Forgot to state that I am using jboss 4.0.4.GA app server with the ejb3-clustered configuration.
I have the same problem. Enviroment:
Interceptor don't work until bean implements interface marked with @Remote or @Local annotation.
I would like this fixed as well. It took me a very long time before I figured out the problem.
Hi @ all!
The problem still exists in JBoss 4.2.1 GA. The only workarround is to add a @Local or @Remote to the interface (like xslava wrote already). We generate our interface with wsimport, so we have to change the generated source code every time we do a new generation. If I understood the JSR-220 right, it should be possible to add interceptors to web-service methds as well (without a @Local or @Remote). If I use GlassFish instead of JBoss to deploy the same .jar-file, all interceptors get called.
Sorry for the "me too" post, but this is really unfortunate. @Interceptors just plain don't work on beans marked with only @Stateless and @WebService. Add @Service, @Local or @Remote, it works fine.
This is on AS 4.2.2.
Has this at least been added to the bug list? Are there any other workarounds?
Please do a search on JIRA (under EJBTHREE Project), and if you cannot find an issue, go ahead and file one. If you attach an isolated test case exhibiting this problem, that's very helpful.
For extra credit, you can even poke around and see what the differences between working @Interceptors and you case is. See http://wiki.jboss.org/wiki/Wiki.jsp?page=DevEJB3NewPlugin.
THREE years and still unfixed?