[
https://issues.apache.org/jira/browse/CXF-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638536#comment-17638536
]
Jens Kleine-Herzbruch commented on CXF-8797:
--------------------------------------------
Hi [~reta], that's yet another issue, then, however. What I was reporting was
actually with NameBinding on the operations level, only I'm not using it on the
*interface* that carries the usual JAX-RS annotations, but the *implementation*
of that interface.
> NameBinding ignored when implementing interface
> -----------------------------------------------
>
> Key: CXF-8797
> URL: https://issues.apache.org/jira/browse/CXF-8797
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.5.4, 3.4.9
> Reporter: Jens Kleine-Herzbruch
> Assignee: Andriy Redko
> Priority: Major
> Fix For: 4.0.0, 3.6.0, 3.5.5, 3.4.10
>
>
> I have the following setup:
> 1. An interface that carries most of the JAX-RS annotations ({{@Path}},
> {{@GET}}, etc.). This interface is provided by a third party.
> 2. A service implementing this interface. This is what I'm developing myself.
> It does not carry any JAX-RS annotations itself.
> 3. A provider ({{ContainerResponseFilter}} in my case) that I now want to
> attach to some of the operations with {{@NameBinding}}.
> Obviously, I can only add the {{@NameBinding}} annotation to the
> implementation class. It looks to me like CXF is only checking against the
> interface carrying the main JAX-RS annotations at runtime, however, so the
> filter is never called.
> If I remove the NameBinding entirely and run the filter as a global filter,
> it works as expected, but of course that's not the intent here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
