Hi Lesley, The alternate addresses in the WSDLs are indeed used by default, but you can override this by specifying an alternate address list in the config.
See the FailoverAddressOverrideTest[1] and particularly the associated config[2] for details. Cheers, Eoghan [1] http://svn.apache.org/repos/asf/cxf/trunk/systests/uncategorized/src/test/java/org/apache/cxf/systest/clustering/FailoverAddressOverrideTest.java [2] http://svn.apache.org/repos/asf/cxf/trunk/systests/uncategorized/src/test/java/org/apache/cxf/systest/clustering/failover_address_override.xml On 26 February 2010 10:59, LTay <[email protected]> wrote: > > Hi all, > > Finally managed to figure out how to get failover working for my client. > The > problem I'm running into now is that when the client does failover to an > alternate address, it uses the address that is in the wsdl. > > But I'd rather not hardcode the actual addresses in the wsdl (would rather > get it from a database config table) and set the endpoint address either at > deployment/runtime. Also I need to configure a few things such as read and > connection timeouts and disable host name checking on the client by doing > this: > > Client client = ClientProxy.getClient(proxy); > HTTPConduit conduit = (HTTPConduit) client.getConduit(); > TLSClientParameters tlsClientParameters = new TLSClientParameters(); > tlsClientParameters.setDisableCNCheck(disableHostNameCheck); > conduit.setTlsClientParameters(tlsClientParameters); > > I can do this for the very 1st port used, since I can set up the client > proxy before passing it on to be used. But not for the succeeding ports > when > failing over. > > Has anyone come across this and been able to maybe inject a client proxy > into the FailoverTargetSelector perhaps? > > Thanks, > Lesley > -- > View this message in context: > http://old.nabble.com/Setting-up-ClientProxies-to-use-for-Failover-tp27716894p27716894.html > Sent from the cxf-user mailing list archive at Nabble.com. > >
