[
https://issues.apache.org/jira/browse/CXF-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665236#action_12665236
]
Andrzej Michalec commented on CXF-1991:
---------------------------------------
Hi Sergey,
I was aware of decoupling them and indeed they are already done similar way:
JAXRSInvoker recursivelly put on stack ORIs and the stack itself is register
insinde inbound Message (uder key being stack's class object; same as other
objects, it's mimics of surrounding code doing things this way). From
UriInfoImpl side it can extracts stack from Message already passed through
constructor -- from this perspective no other changes are introduces on the way
from JAXRSInvoker to UriInfoImpl.
I could not find better point of stack generation that invoker itself, since
invoker is responsible for lookup for resources -- what's your suggestion?
Where is other control point to put ORI on stack?
Or maybe let me finish this unit of work and once patch is submitted you can
help me improving it :)
cheers,
andy.
> Incomplete implementations of UriInfo and UriBuilder
> ----------------------------------------------------
>
> Key: CXF-1991
> URL: https://issues.apache.org/jira/browse/CXF-1991
> Project: CXF
> Issue Type: Bug
> Components: REST
> Affects Versions: 2.1.3, 2.2
> Reporter: Andrzej Michalec
> Priority: Minor
>
> Some useful methods like UriBuilder.path(Class), UriBuilder.path(Method) or
> UriInfo.getMatchedResources() are not implemented so far.
> Since I am have my locally tuned versions of these classes I am going to
> provide patch soon :)
> cheers,
> andy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
