On 31/01/13 16:13, Ivan.Latysh wrote:
Aki Yoshida-3 wrote
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?
Unfortunately not, the app is shipped to the client, and client configure it
in a single place. So I do not know the name or the port until app is
deployed.
I wonder, how comes that config parameter got into the bean name ?
Cause ... bean can have multiple names and what if I have a comma in my path
?
Can you clarify this bit please ?
Cheers, Sergey
Why not to have a regular parameter that avoid all that confusion and
limitations ?
--
View this message in context:
http://cxf.547215.n5.nabble.com/cxf-http-conduit-with-parameterizable-name-tp5722488p5722559.html
Sent from the cxf-user mailing list archive at Nabble.com.
