L.S.,

I just wanted to make sure that the actual address used in the CXF endpoint
configuration matched the one in http.nonProxyHosts, but I would have
expected your current configuration to work.  Not entirely sure what's
going wrong here.  One other solution you might want to consider is to
configure the CXF HTTP Conduit itself with the proxy parameters - looking
at https://issues.apache.org/jira/browse/CXF-2839, it looks like it at
least support those properties as well as the setting for non-proxy hosts
are available on the conduit itself.

BTW, did you consider the repository manager solution I mentioned?  That's
commonly used because it also helps you in the (usual Maven-based)
development of the application bundles themselves.


Regards,

Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/


On Tue, Dec 4, 2012 at 4:23 PM, attilav <[email protected]> wrote:

> Hi,
>
> Thanks for your replies.
>
> The fourth option (.m2/settings.xml) I already tried - and it would not
> work. I mean it has the same effect as setting the proxy in
> system.properties - it still redirects cxf to the proxy.
>
> Gert, what do you mean by "exact same address format"?
>
> In my beans.xml I have
>     <cxfbc:provider wsdl="classpath:/wsdl/PNM-FDL.wsdl"
>                           locationURI="http://10.11.12.13:8001/PMSEvent";
>                           service="pms:PMSServiceSoap"
>                           endpoint="PMSServiceSoap"
>                           useJBIWrapper="false"
>                           >
>     </cxfbc:provider>
>
> In the system.propreties I put:
> http.nonProxyHosts=10.11.12.13
>
>
> As for the upgrade option, I am already planning the upgrade to 4.4,
> however
> that takes time, as I have to retest quite a number of applications.
>
> regards,
> Attila
>
>
>
> --
> View this message in context:
> http://servicemix.396122.n5.nabble.com/Servicemix-proxy-question-tp5715059p5715143.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>

Reply via email to