The location of the configuration files has changed (as a result of the Benson's effort), here're the updated links :
http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/security/jaxrs-https.xml and http://svn.apache.org/repos/asf/cxf/trunk/systests/jaxrs/src/test/java/org/apache/cxf/systest/jaxrs/security/jaxrs-https-url.xml cheers, Sergey Sergey Beryozkin wrote: > > Hi Paul > > After talking to Dan I've realized that you can already limit an > http-conduit configuration to individual URIs. > > For example, if the endpoint address starts with > "http://books:9095/bookstore"; then one can do : > > <http:conduit name="http://books:9095/bookstore.*"/> > > This way you can have conduits for production and test URIs (as proposed > by Dan). > > Additionally, one can also have http conduits identified similarly to the > way they're identified for SOAP-based clients. > > For WebClients you can do : > > <http:conduit name="{http://books:9095/bookstore}WebClient.http-conduit"/> > (in 2.2.3 the local name is 'WebResource', I updated it to 'WebClient' ) > > > For proxies you can do : > > <http:conduit > name="{http://jaxrs.systest.cxf.apache.org/}BookStore.http-conduit"/> > > (in 2.2.3 additional 'jaxrs' suffix is added tp the namespace, I remoced > it on the trunk ) > > where 'jaxrs.systest.cxf.apache.org' is a reverse package name > > I'm also thinking of letting users to directly inject an HTTPConfigPolicy > instances during the creation time for simple cases. Also, I added > ClientConfiguration.getHttpConduit() to avoid casts - for JAXRS it will be > HTTP in most cases.. > > Please see updated > > http://svn.apache.org/repos/asf/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/jaxrs/security/jaxrs-https.xml > > and > > http://svn.apache.org/repos/asf/cxf/trunk/systests/src/test/java/org/apache/cxf/systest/jaxrs/security/jaxrs-https-url.xml > > thanks, Sergey > > > > Paul Wilton wrote: >> >> Hi >> >> I am using org.apache.cxf.jaxrs.client.WebClient to access a REST >> service that sits behind a squid proxy server. The rest client WebClient >> is running on Tomcat. >> >> I have set JAVA_OPTS in the catalina startup script with my proxy server >> settings: >> -Dhttp.proxyHost=my.proxy.domain >> -Dhttp.proxyPort=80 >> -Dhttp.nonProxyHosts=localhost,127.0.0.1 >> >> But the requests do not make it past the proxy server, and I just get >> socket connection timeouts >> >> Just to clarify, >> My WebClient works fine when not behind a proxy server, and I can also >> access the restful service using curl -x on the command line giving the >> same proxy details. >> >> My questions: >> Does WebClient handle proxy servers ok ? >> Is passing the proxy details to the JVM using java opts a valid >> technique with WebClient ? >> Is there some specific way of configuring WebClient to use proxy servers >> ? >> >> Thanks for any help >> Paul >> This e-mail (and any attachments) is confidential and may contain >> personal views which are not the views of the BBC unless specifically >> stated. If you have received it in error, please delete it from your >> system. Do not use, copy or disclose the information in any way nor act >> in reliance on it and notify the sender immediately. >> >> Please note that the BBC monitors e-mails sent or received. Further >> communication will signify your consent to this >> >> This e-mail has been sent by one of the following wholly-owned >> subsidiaries of the BBC: >> >> BBC Worldwide Limited, Registration Number: 1420028 England, Registered >> Address: BBC Media Centre, 201 Wood Lane, London, W12 7TQ >> BBC World News Limited, Registration Number: 04514407 England, Registered >> Address: BBC Media Centre, 201 Wood Lane, London, W12 7TQ >> BBC World Distribution Limited, Registration Number: 04514408, Registered >> Address: BBC Media Centre, 201 Wood Lane, London, W12 7TQ >> >> > > -- View this message in context: http://www.nabble.com/using-jax-rs-WebClient-through-proxy-server-tp25169942p25237457.html Sent from the cxf-user mailing list archive at Nabble.com.
