-
Bug
-
Resolution: Done
-
Major
-
27.0.0.Alpha1, 26.1.1.Final
An EJB client can send and receive ContextData via an Interceptor, see addReturnedContextDataKey(String key) method on the EJBClientInvocationContext class, see:
/** * Indicates to the server that a client side interceptor is interested in the context data that is stored * under the given key. Any object on the context data map (i.e. {@code InvocationContext.getContextData()} that is * present at the end of the server invocation will be serialised and returned to the client. * * If an object is present under this key and is not serializable then the request will fail. * * @param key The context data key the client interceptor is interested in */ public void addReturnedContextDataKey(String key) { Object returnedData = getContextData().get(RETURNED_CONTEXT_DATA_KEY); if(returnedData == null) { getContextData().put(RETURNED_CONTEXT_DATA_KEY, returnedData = new HashSet<>()); } else if(!(returnedData instanceof Set)) { throw Logs.INVOCATION.returnedContextDataKeyOfWrongType(); } Set<String> keys = (Set<String>) returnedData; keys.add(key); }
If a client is sending a key/value to the server and add this key with addReturnedContextDataKey(String key), a server side removed value for that key is still contained in the ContextData of the EJB response.
- is cloned by
-
JBEAP-23784 [GSS](7.4.z) WFLY-16567 - EJB response contain ContextData that has been removed on the server side
- Closed
- is related to
-
WFLY-16796 LocalEjbReceiver response contains ContextData that has been removed on the server side
- Closed
- relates to
-
WFLY-16763 Remove all ContextData on client and server that is not defined using 'jboss.returned.keys'
- Open