[CXF-8227] Failure to comply with JAX-RS spec with ContainerRequestContext and WriterInterceptorContext

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.3.5, 3.2.14, 3.4.0
• Fix Version/s: 3.5.0, 3.3.8, 3.4.1
• Component/s: JAX-RS

Environment

• Linux and or Windows
• Java 11.0.6
• CXF 3.3.5

• Estimated Complexity: Unknown
• Assignee: Andriy Redko
• Reporter: Jorge Cercas
• Created: 26/Feb/20 22:57
• Updated: 19/Mar/24 01:17
• Resolved: 10/Sep/20 15:54

Description

The Javadoc for the ContainerRequestContext interface says:
setProperty(String name, Object object)
Binds an object to a given property name in the current request/response exchange context.
getProperty(String name)
Returns the property with the given name registered in the current request/response exchange context, or null if there is no property by that name.

And the Javadoc for the InterceptorContext interface and known sub-interfaces (ReaderInterceptorContext, WriterInterceptorContext) says:
setProperty(String name, Object object)
Binds an object to a given property name in the current request/response exchange context.
getProperty(String name)
Returns the property with the given name registered in the current request/response exchange context, or null if there is no property by that name.
 
However, given the code below for a resource that does provide an entity, the variable fooBar in the aroundWriteTo method is always null.

// code placeholder
@Provider
public class InterceptorBug implements ContainerRequestFilter, WriterInterceptor {
    
    @Override
    public void filter(ContainerRequestContext requestContext) throws IOException {
        requestContext.setProperty("foo.bar", "baz");
    }

    @Override
    public void aroundWriteTo(WriterInterceptorContext context) throws IOException, WebApplicationException {
        context.proceed();
        // 'fooBar' ALWAYS NULL
        var fooBar = context.getProperty("foo.bar");
    }
}

Issue Links

• links to: GitHub Pull Request #692