Ok, thanks for the update Jim.
I'm gonna check in Pax URL to see it's the really the case.
Pax URL should use a dedicated System property and remap it in
http.proxy only when required.
Let me check.
Regards
JB
On 08/08/2011 05:53 PM, Jim Talbut wrote:
That is what I mean, yes.
I don't know about "all", but the CXF connections I was initiating were
affected.
Thank
Jim
-----Original Message-----
From: Jean-Baptiste Onofré [mailto:[email protected]]
Sent: 08 August 2011 16:33
To: [email protected]
Subject: Re: Karaf picks up Maven proxy settings and makes them system
properties
Hi Jim,
do you mean that the http.proxy in your M2 settings.xml affect "all"
HTTP connections ?
It looks like Pax Url Mvn "push" the http.proxy settings in the System
properties (whereas it shouldn't do that).
Regards
JB
On 08/08/2011 05:29 PM, Jim Talbut wrote:
Hi,
I've just spent the last couple of hours trying to work out why a CXF
web service client, accessed via Camel and hosted via Karaf was unable
to communicate with the target service.
Eventually I found that the system property http.proxyPort was set and
was being pulled from .m2/settings.xml.
I'm not sure who is to blame for this, but it's really obscure behaviour.
Is this unavoidable?
Jim
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
