On 18/06/14 16:41, gquintana wrote:
After debugging the code, I think the problem is that (as of CXF 2.6.14), the HttpConduitBeanDefinitionParser defines a Spring bean with name="${something}". As this name is also the bean Id from the Spring bean factory point of view it is never postprocessed by the property placeholder. As a result I have in the Spring bean factory an HTTP conduit name "${something}" instead of "http://something.com";.Then the HTTPTransportFactory#configure looks for a Conduit with 1) id="{namespace}port.http-conduit" (I can't do that because I have several Rest providers with same interface but different auth params) 2) id="http://something.com"; which can't succeed since bean is still named "${something}" Did I miss/misunderstood something?
Right, we are talking about https://issues.apache.org/jira/browse/CXF-4811 recently duplicated by Raul too: https://issues.apache.org/jira/browse/CXF-5320 Hopefully we will get it resolved soon Thanks, Sergey
-- View this message in context: http://cxf.547215.n5.nabble.com/JAXRS-client-proxy-and-HTTP-Conduits-tp5745021p5745324.html Sent from the cxf-user mailing list archive at Nabble.com.
-- Sergey Beryozkin Talend Community Coders http://coders.talend.com/ Blog: http://sberyozkin.blogspot.com
