Hi, Would you please raise a jira ticket and append your test case if possible there?
My gut now is we also need TLSClient|ServerParametersHolder where we can use ValueMetadata to do properties substitution. －－－－－－－－－－－－－ Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat On 2014-3-11, at 下午12:25, carma.robot wrote: > Hi Freeman, > > Yes, I meant CXF version 2.7.4. Sorry for the confusion. > > I'm also aware of the JIRA ticket that you mentioned. I tried upgrading to > version 2.7.7 and noticed the same exact issue. In fact, I also tried > upgrading to 2.7.10 and, even though I had to deal with some interesting > dependency issues, that did not help either. > > Is there anything else I could try? Am I missing something? What is the best > way to troubleshoot this? If you can point me to a place in the CXF code > where it makes sense to put a break point then I'd be glad to spend some > time troubleshooting this with a debugger. > > Alternatively, is HTTPTransportActivator something I could use to work > around this problem? > > I appreciate the response and I really hope you can help me out with this. > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Blueprint-property-placeholder-does-not-work-with-HTTP-conduit-configuration-tp5740946p5741060.html > Sent from the cxf-user mailing list archive at Nabble.com.
