Forum Discussion
GDow
12 years agoOccasional Contributor
Hi Temil, thanks for your response.
I found the blog post that you mention, and I used that to get the fix for ONE soap request.
Maybe I should have phrased my question a bit differently.
What would be the best way to do the following to cover ALL soap requests, without going into every single soap request and changing them:
SmartBear's own HowTo page, http://www.soapui.org/SOAP-and-WSDL/usi ... ssing.html, says the following:
"All fields in the tab support property-expansion, allowing you to easily pull values from properties defined at a higher level in your project", but I can't see how to do that. Can you tell me how to do this?
Thanks
amorps
I found the blog post that you mention, and I used that to get the fix for ONE soap request.
Maybe I should have phrased my question a bit differently.
What would be the best way to do the following to cover ALL soap requests, without going into every single soap request and changing them:
- check Enable WS-A addressing
- check Add default wsa:Action
- check Add default wsa:To
SmartBear's own HowTo page, http://www.soapui.org/SOAP-and-WSDL/usi ... ssing.html, says the following:
"All fields in the tab support property-expansion, allowing you to easily pull values from properties defined at a higher level in your project", but I can't see how to do that. Can you tell me how to do this?
Thanks
amorps
Related Content
- 12 years agosastowe
- 5 years agorancan
- 11 years agoRyan_Moran