-
1. Re: EJB Client interceptor not called
wdfink Jul 24, 2013 1:23 PM (in response to claudio4j)Hello Claudio,
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?
-
2. Re: EJB Client interceptor not called
claudio4j Jul 24, 2013 2:12 PM (in response to wdfink)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 ?
Thanks
Claudio -
3. Re: EJB Client interceptor not called
wdfink Jul 25, 2013 2:32 PM (in response to claudio4j)Hi Claudio,
I'll check whether there is a possibility
-
4. Re: EJB Client interceptor not called
jmartisk Aug 15, 2013 5:54 AM (in response to wdfink)I created a feature request for that: https://issues.jboss.org/browse/EJBCLIENT-90
-
5. Re: EJB Client interceptor not called
piotr.kucia Nov 27, 2014 5:25 PM (in response to claudio4j)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
-
6. Re: EJB Client interceptor not called
mrudulav Feb 13, 2017 11:53 PM (in response to claudio4j)Hi Claudio,
You found a solution for this problem? I am facing the same issue now.