Steve Cohen schrieb:
Please forgive my previous snark. It's been a long night.
I overlooked possibility 4, that I'm an idiot. I simply wasn't
getting all my other configuration parameters right, so I don't really
know that the cxf.config.file definition mechanism wasn't working. I
suspect it probably is.
Your points are well-taken and in a perfect world I'd agree. My
situation sucks, frankly. I work for a tiny underfunded backwater of
a mega-corporation that won't spend and wants to exploit open-source
without giving enough back in my opinion. The vendor is helping in
his way, but then tells me stuff like "change your build process",
"use Spring". My snark is better directed his way. The whole issue
would go away if he would let me use the same credentials on his
development and test systems.
Hi Steve,
it is perfectly normal that configurations on develop and test systems
are different. By using the spring PropertyPlaceHolderConfigurer in your
cxf.xml you can externalise the username and password from this file.
<bean id="propertyConfigurer"
class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
<property name="locations">
<list>
<value>classpath:config.properties</value>
</list>
</property>
</bean>
This allows you to use ${propertyname} in the file. For example:
<http:conduit name="{http://some.com/service}port.http-conduit";
<http://some.com/service%7Dport.http-conduit%22>;>
<http:authorization>
<sec:UserName>${username}</sec:UserName>
<sec:Password>${password}</sec:Password>
</http:authorization>
</http:conduit>
You can also replace the url of the service this way. So you can use one wsdl
that contains a dummy url and replace the url for develop, test and production.
I hope this will solve your problem.
Greetings
Christian
Please forgive me from using you guys as a punching bag.
--
Christian Schneider
---
http://www.liquid-reality.de
