[
https://issues.apache.org/jira/browse/CXF-8408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263745#comment-17263745
]
Andriy Redko commented on CXF-8408:
-----------------------------------
Thanks [~amccright] , I think we could close this one and indeed create a
feature request, what do you think guys?
> Response.getLocation() returns null after update from CXF 3.3.6 to 3.4.1
> ------------------------------------------------------------------------
>
> Key: CXF-8408
> URL: https://issues.apache.org/jira/browse/CXF-8408
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 3.4.1
> Reporter: Jörg Hohwiller
> Priority: Major
>
> javax.ws.rs.core.Response.getLocation() used to return the URL of the service
> invoked. We used this information to enhance the error handling via a custom
> org.apache.cxf.jaxrs.client.ResponseExceptionMapper since CXF lacks to
> provide contextual information in error scenarios making it hard to use in
> productive environments when service client invocations fail without
> contextual information available.
> After we now updated from 3.3.6 to 3.4.1 one of our tests failed with an NPE
> since response.getLocation() now returns null instead of the correct URL and
> we were doing url.toString() on that without checking for null.
> I am working on ugly workarounds (casting to ResponseImpl and getting the
> Conduit to retrieve at least the base URL) but it would be great if CXF could
> fix this regression bug at the root.
> [https://github.com/devonfw/devon4j/pull/310/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
