[
https://issues.apache.org/jira/browse/CXF-6998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15411607#comment-15411607
]
ASF GitHub Bot commented on CXF-6998:
-------------------------------------
Github user sberyozkin commented on the issue:
https://github.com/apache/cxf/pull/154
Hi Andriy
That spec statement is many years old, coming form 1.1 or earlier, before
ApplicationPath was introduced (AFAIK) thus one may say well that statement
does not apply to ApplicationPath as it is really about the resource classes
and methods.
(FYI, CXF checks class/interface level Path itself and never had any issues
with various TCKs.)
I'd say it should def be valid to have a custom Application extending
another custom Application with ApplicationPath. So IMHO the patch is safe
enough :-)
Sergey
> Manual resolve ApplicationPath from parent classes as well.
> -----------------------------------------------------------
>
> Key: CXF-6998
> URL: https://issues.apache.org/jira/browse/CXF-6998
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Reporter: John D. Ament
>
> The ApplicationPath annotation is not inherited. As a result, when proxies
> are used (for things like CDI integration), those proxies do not have the
> application path defined. As a result, the base URI is ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
