Aki Yoshida-3 wrote > I was wondering why you can't (or don't want to) configure the > http.proxy setting once per VM.
Some connections are with applications in external networks - here we need the proxy - and some with others in the same network. Also, our web app may invoke itself in certain scenarios. Our idea is to avoid the proxy (and the reverse proxy) as a means of optimization in cases were connections are rather "internal". Leaving that aside, we could well configure the proxy setting per VM. As to your suggested solution, I'm wondering wether proxy settings take effect before or after the client stub is created. Setting the proxy using HTTPClientPolicy has never been a problem. It's only that accessing the WSDL when the client stub is instantiated (new EksService(wdslUrl)) fails and I've found no way to set the proxy on a per-instance basis to deal with that case. -- View this message in context: http://cxf.547215.n5.nabble.com/HTTP-proxy-problem-with-wsdl-first-client-tp5743760p5744159.html Sent from the cxf-user mailing list archive at Nabble.com.
