Yea, your previous question pointed me in the cxf direction. Are there any negatives to using one implementation over the other since client timeouts appear proprietary any ways.
On Tue, Apr 14, 2015 at 11:06 AM, Romain Manni-Bucau <[email protected]> wrote: > You can set the timeout to cxf http conduit. > > If you really want jersey try add in a > WEB-INF/classes/META-INF/services/javax.ws.rs.client.ClientBuilder with the > line: > > org.glassfish.jersey.client.JerseyClientBuilder > > > > 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-14 16:25 GMT+02:00 sgjava <[email protected]>: > > > org.apache.cxf.jaxrs.client.spec.ClientImpl > > > > > > > > -- > > View this message in context: > > > http://tomee-openejb.979440.n4.nabble.com/javax-ws-rs-client-Client-read-timeout-not-working-tp4674416p4674420.html > > Sent from the TomEE Users mailing list archive at Nabble.com. > > > -- Steven P. Goldsmith
