[CXF-7630] NameBindings are ignored for (at least) ContextResponseFilters

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.2
• Fix Version/s: 3.2.2, 3.1.15
• Component/s: JAX-RS
• Estimated Complexity: Unknown
• Assignee: Sergey Beryozkin
• Reporter: Carlos Sierra Andrés
• Created: 01/Feb/18 17:09
• Updated: 07/Feb/18 14:52
• Resolved: 02/Feb/18 13:10

Description

If we create a NameBinding annotation:

@NameBinding
@Retention(RetentionPolicy.RUNTIME)
@Target({ElementType.TYPE, ElementType.METHOD})
public @interface Filtered {
}

and qualify a ContainerResponseFilter:

@Filtered
@Provider
public class TestNameBoundFilter implements ContainerResponseFilter {

    @Override
    public void filter(
            ContainerRequestContext requestContext,
            ContainerResponseContext responseContext)
        throws IOException {

        MultivaluedMap<String, Object> headers = responseContext.getHeaders();

        headers.putSingle("NameBoundFiltered", "true");
    }

}

and some methods in a Resource:

public class NameBoundResource {

    @GET
    @Filtered
    @Path("/filtered")
    public String filtered() {
        return "filtered";
    }

    @GET
    @Path("/unfiltered")
    public String unfiltered() {
        return "unfiltered";
    }

}

only responses for requests made to "/filtered" path should carry the "NameBoundHeader" header. However both responses, to "/filtered" and "/unfiltered" carry the header.

Issue Links

• links to: GitHub Pull Request #376