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
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
