OK Dan, I finally got back to this problem I was having and thought I would
post what I've found in case you have a simple solution. Spring property
resolution works fine for http:client http:proxyAuthorization and
http:tlsClientParameters as you said...however...
What I found is that having a property for ProxyPort
i.e.
<http:client AllowChunking="false" ProxyServer="${proxyServer}"
ProxyServerPort="${proxyPort}"/>
seems to fail schema validation before the property has a chance to be
replaced since the ProxyServerPort is defined as an xs:int in
http://cxf.apache.org/schemas/wsdl/http-conf.xsd
Here is the relevant snippet of the exception
Exception in thread "Primary Chain"
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
24 in XML document from class path resource [app-context.xml] is invalid;
nested exception is org.xml.sax.SAXParseExcep
tion: cvc-datatype-valid.1.2.1: '${proxyPort}' is not a valid value for
'integer'.
If I hard code proxyPort to say 8080 but leave ProxyServer as a Spring
property, everything works fine and the property is resolved.
Perhaps I am missing something simple... Any ideas on how I can externalize
the proxy port as a spring property?
--
View this message in context:
http://www.nabble.com/Are-properties-not-resolved-in-http%3Aconduit-tp20444369p22706352.html
Sent from the cxf-user mailing list archive at Nabble.com.
