I've done the below using spring placeholders to swap out the server name just fine. You may need to debug into the CXF code that is actually building the HttpConduit from the spring to double check the actual URL you need to put into there because when I did it I remember it being sensitive in what it expected there.
________________________________________ From: Ivan.Latysh [[email protected]] Sent: Wednesday, January 30, 2013 6:25 PM To: [email protected] Subject: Re: <cxf-http:conduit/> with parameterizable name Hello All! Re-posting, XML is visible on Nabble, but disappeared in the mail. I have a simple case when a client consume a few services, and for each service I have configured a corresponding conduit. But I am having a real hard time creating conduit name from a parameters. Hypothetical config: <cxf-http:conduit name="http://${server1.name}:${server1.port}/services/*";> ... </cxf-http:conduit> <cxf-http:conduit name="http://${server2.name}:${server2.port}/services/*";> ... </cxf-http:conduit> Is there are a way to configure conduit without hard-coding service URL's ? P.S. I know that I can do: <cxf-http:conduit name="*.http-conduit"> ... </cxf-http:conduit> but it does not work, as each conduit has it's own authentication model. Any ideas ? -- View this message in context: http://cxf.547215.n5.nabble.com/cxf-http-conduit-with-parameterizable-name-tp5722488p5722529.html Sent from the cxf-user mailing list archive at Nabble.com.
