3 Replies Latest reply on Jul 3, 2012 1:42 PM by Wesley Janik

    Client EJB interceptor problem - Context data deserialized to private data map on server side.

    Michael Gronau Newbie

      Hello,

      I'm facing a problem with ejb interceptors. On the client side we put some custom data to the EJBClientInvocationContext with EJBClientInvocationContext.getContextData().put(...). This data map is serialized as attachments into the invocation stream. On the server side we have a standard ejb interceptor which tries to read this custom data with context.getContextData().get(...). Some debugging has shown, that the ContextData map on the server side is deserialized into the 'privateData' map (via readAttachements) to the enclosing InterceptorContext instance of the current InvocationContext. So we cannot access this data from within our interceptor. Is this by design or a bug?

       

      Thanks alot,

       

      Michael