as you are using a scoped-context the EJBClientContext is different to EJBClientContext.getCurrent().
At the moment it is not simple possible to add the inteceptor to the context.
What it the use-case behind? Is the registration and the invocation in the same context?
Hi Wolf-Dieter, the use case is a web application, protected by a security domain, the user authenticates to this security domain and enter application. Then this webapp looks up a EJB deployed elsewhere. That EJB is protected by a security domain. That EJB receives the credential authenticated in the webapp, the quickstart has more details to this subject.
I will change the code to use the outbound connections of remoting subsystem, that way I am sure the EJB Client Interceptor is called.
Do you plan to make EJB client interceptor works with scoped contexts EJB calls ?
I'll check whether there is a possibility
EJBCLIENT-90 is still unresolved, but as far as i discovered you still can register interceptor for scoped context via ServiceLoader mechanism (at least on WildFly 8.1.0.Final).
EJBClientContexts load interceptor class specified in META-INF/services/org.jboss.ejb.client.EJBClientInterceptor
You found a solution for this problem? I am facing the same issue now.