Yes, it is supported.
Starting from 3.1.x, JAX-RS 2.0 matching at the class resource level is
properly supported for cases where multiple class resources have the
identical Path value, was too sensitive to address it for 3.0.x.
Other than that, if multiple class resources have different path values
then the class resource which wins will be considered further for the
actual method, no backtracking will be made...
Sergey
On 11/05/16 19:36, asookazian wrote:
so the new jaxrs:servicebean class endpoints are now working. previously
they were configure as a ref/component on the same address as the existing
service/class (which apparently is illegal but I saw no exception in the log
when i updated the bundle in karaf).
the existing BP config.xml has the same issue:
<jaxrs:server id="EventRegistryRS" address="/mm/er">
<jaxrs:serviceBeans>
<ref component-id="foo"/>
<ref component-id="bar"/>
</jaxrs:serviceBeans>
<jaxrs:providers>
<ref component-id="filter1"/>
<ref component-id="provider1"/>
<ref component-id="provider2"/>
</jaxrs:providers>
</jaxrs:server>
foo extends bar in this case. the existing methods/endpoints for that
original class/service are working. when I add the new methods, they show
up in the WADL but I get 404 on GET requests.
is it legal/ok to list more than one component in the <jaxrs:serviceBeans>
section above? How does cxf know which class to route to based on that
particular address?
--
View this message in context:
http://cxf.547215.n5.nabble.com/No-operation-matching-request-path-tp556149p5768585.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
