Hi!
Currently cxf (3.1.10) runtime sets default message encoding, if not
specified by client, to
ISO-8859-1
String encoding = (String)message.get(Message.ENCODING);
if (StringUtils.isEmpty(encoding)) { // this is never working
encoding = StandardCharsets.UTF_8.name();
Thanks for your replay!
I see http://cxf.apache.org/docs/asynchronous-client-http-transport.html.
It is said when "use.async.http.conduit" is true, the HttpAsyncClient will
be used even for synchronous calls and "use.async.http.conduit" is false,
asynchronous calls will rely on the traditional
Hi,
Is there a link or a dependency management url where I can pull the 3.1.11
version?
Thanks
-Sonam
-Original Message-
From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Sent: Tuesday, March 28, 2017 9:59 AM
To: users@cxf.apache.org
Subject: Re: How to transprot by HttpClient
It will also work with CXF 3.1.11 to be released in a few weeks
Sergey
On 28/03/17 16:19, Sonam Samdupkhangsar wrote:
When will the CXF 3.2.0 cxf-spring-boot-starter-jaxrs be realeased to maven
central?
I am using SpringBoot 1.5.2 with cxf jaxrs 3.1.7 and I keep getting
When will the CXF 3.2.0 cxf-spring-boot-starter-jaxrs be realeased to maven
central?
I am using SpringBoot 1.5.2 with cxf jaxrs 3.1.7 and I keep getting
ClassNotFoundException:
org.springframework.boot.context.embedded.ServletRegistrationBean error.
3.2.0-SNAPSHOT fixes the error.
Thanks
Thanks for your replay!
I see http://cxf.apache.org/docs/asynchronous-client-http-transport.html.
It is said when "use.async.http.conduit" is true, the HttpAsyncClient will
be used even for synchronous calls and "use.async.http.conduit" is false,
asynchronous calls will rely on the traditional
Hi
One needs to set a "use.async.http.conduit" JAXWS or JAXRS property to
use it for the sync calls.
See also
http://cxf.apache.org/docs/asynchronous-client-http-transport.html
Sergey
On 27/03/17 07:29, cctv092 wrote:
Hi all,
As we know, cxf uses a transport based on the in-JDK
