cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-7338) WebClient, map response Content-Type to other types
Date Tue, 18 Apr 2017 14:34:41 GMT

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

Sergey Beryozkin commented on CXF-7338:
---------------------------------------

CXF interceptors can not be registered as JAXRS providers, one would need to register them
with JAXRSClientFactoryBean or WebClient.getConfig(client), may be this is why it did not
work. But yes, it it works with ClientResponseFilter then it is good 

> WebClient, map response Content-Type to other types
> ---------------------------------------------------
>
>                 Key: CXF-7338
>                 URL: https://issues.apache.org/jira/browse/CXF-7338
>             Project: CXF
>          Issue Type: Wish
>          Components: JAX-RS
>    Affects Versions: 3.1.9
>            Reporter: Anton Johansson
>            Assignee: Sergey Beryozkin
>
> I'm communicating with a third party provider and I'm using CXF (WebClient), like I always
do. But this third party provider has messed up slightly. Even if the contents actually is
XML, they return Content-Type text/html;charset=ISO-8859-1.
> So I would like the possibility to tell my client to treat text/html as application/xml
in this specific scenario, maybe using:
> {code:java}
> client.map("text/plain", "application/xml").post(data);
> {code}
> If there's another solution or workaround that I've missed, please let me know!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message