Forum Discussion
SmartBear_Suppo
16 years agoSmartBear Alumni (Retired)
Hi!
Has the namespace changed in the updated wsdl? If so, this is expected behaviour, the updating of requests in this scenario requires the same namespace/element/node structure to work. soapUI Pro has refactoring functionality (http://www.soapui.org/userguide/interfa ... oring.html) for handling this, check it out.
If the namespace and element/node structure is the same in both the old and new wsdl, then this sounds like a bug, so I kindly ask you to attach the old and new wsdls, together with a sample message that is not getting updated correctly, so I can reproduce and fix!
regards!
/Ole
eviware.com
Has the namespace changed in the updated wsdl? If so, this is expected behaviour, the updating of requests in this scenario requires the same namespace/element/node structure to work. soapUI Pro has refactoring functionality (http://www.soapui.org/userguide/interfa ... oring.html) for handling this, check it out.
If the namespace and element/node structure is the same in both the old and new wsdl, then this sounds like a bug, so I kindly ask you to attach the old and new wsdls, together with a sample message that is not getting updated correctly, so I can reproduce and fix!
regards!
/Ole
eviware.com
Related Content
Recent Discussions
- 20 hours agogroovyguy