[ 
https://issues.apache.org/jira/browse/CXF-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209041#comment-16209041
 ] 

Sergey Beryozkin edited comment on CXF-7527 at 10/18/17 9:21 AM:
-----------------------------------------------------------------

Yes, this is what my original source of confusion was about. 

If you now add "/sub" to BarResource.getBar(), then "GET /foo/bar/sub" will go 
via 1) FooResource resource class - "foo" 2) FooResource.getBarResource() 
subresource locator - "foo/bar" 3) BarResource.getBar() subresource method - 
"foo/bar/sub"

The only difference between the docs example and the above case is that  
BarResource.getBar() has Path("") in the docs (it's implicit but could've been 
there) vs Path("/sub") in my example 


was (Author: sergey_beryozkin):
Yes, this is what was my original source of confusion about. 

If you now add "/sub" to BarResource.getBar(), then "GET /foo/bar/sub" will go 
via 1) FooResource resource class - "foo" 2) FooResource.getBarResource() 
subresource locator - "foo/bar" 3) BarResource.getBar() subresource method - 
"foo/bar/sub"

The only difference between the docs example and the above case is that  
BarResource.getBar() has Path("") in the docs (it's implicit but could've been 
there) vs Path("/sub") in my example 

> JAXRS UriInfo.getMatchedUris does return matched URIs twice for sub resources
> -----------------------------------------------------------------------------
>
>                 Key: CXF-7527
>                 URL: https://issues.apache.org/jira/browse/CXF-7527
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 3.1.12
>            Reporter: Lenoire
>         Attachments: uriinfo-issues.jar
>
>
> Invoking method {{UriInfo.getMatchedURIs()}} return matched resource URI 
> twice when invoked from SubResource method.
> See attachment for a junit test reproducing the issue (=> 
> {{testMatchedUrisFromSubResource()}}) 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to