call org.apache.cxf.jaxrs.client.WebClient#getConfig on your client, then org.apache.cxf.jaxrs.client.ClientConfiguration#getHttpConduit:
WebClient.getConduit(jaxrsClient).getHttpConduit() Side note: when we'll upgrade cxf we'll get the feature you wanted: https://issues.apache.org/jira/browse/CXF-6353 Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-04-20 18:07 GMT+02:00 sgjava <[email protected]>: > OK, I just switched back to the generic javax.ws.rs.client.Client and > removed > the GlassFish stuff and it works. > > final Client client = ClientBuilder.newClient(); > final VersionDto versionDto = new VersionDto("xxx"); > final VersionDto response = > client.target(url).request().post(Entity. > entity(versionDto, MediaType.APPLICATION_JSON), > VersionDto.class); > > Now back to the timeout. In a previous post you said I could get > HttpConduit > from generic javax.ws.rs.client.Client? I noticed client.getConfiguration() > returns org.apache.cxf.jaxrs.impl.ConfigurationImpl. Will I be able to do > use properties from this or do I need to do > conduit.getClient().setReceiveTimeout(7000)? > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/JAX-RS-POJO-mapping-tp4674454p4674523.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
