the name attribute of the conduit corresponds to its bean ID. So you can't use parameters in there like in your example.
if you know at the configuration time which addresses will be called, can you just define a set of pattern matched conduits to switch the setting? 2013/1/31 Ivan.Latysh <[email protected]>: > 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.
