Thanks, Christian.
This certainly sounds like it could be the answer to my dilemma and I
agree wholeheartedly with you that this is a normal scenario that needs
to be supported.
However, I don't fully understand what you are suggesting here.
Something must be a selector (a key) into the list of locations and
passwords and somehow this key needs to be passed to the object doing
the resolution. Is there a fleshed out sample of this anywhere?
Steve
Christian Schneider wrote:
...
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.
