I appreciate your feedback but not only have I tried it that way, I haven't tried it any other way. I'm actually injecting the component into a field of the local interface type, so just calling the method proves that it's available as part of the SFSB. I've also checked the logs to make sure the component is deployed as a conversation scoped SFSB at startup.
I'm in the process of upgrading to CR3 at the moment and I think that might have fixed the problem. After taking a look through the Seam source (Beta 2) I didn't see any reason it would have preferentially intercepted some methods and not others so my theory is that it was a bug in how interceptors were applied in the EJB embedded server that came with that release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3949188#3949188 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3949188 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
