Forum Discussion
KarelHusa
Champion Level 1
The workaround I use for this issue is following:
- select the existing interface (called e.g. "serviceBinding")
- go into "Interface Properties" window and change the Name property (e.g. to "serviceBinding_v1")
- import the second WSDL (which you could not import up to now)
- you get a new interface (e.g. "serviceBinding")
- you can rename the newly created interface similarly as you did in step 2 (e.g. to "serviceBinding_v2")
- the interfaces have a different name, though they have the same binding name
The advantage is that you can distinguish the interfaces between each other. However, you need to be careful and avoid updating the interface, in such a case the interface name would get renamed back to the binding name from the WSDL.
This approach is especially helpful when you need to test or mock multiple versions of the same service within the same SoapUI project.
Best regards,
Karel
Amruthavani
6 years agoSenior Member
This workaround helped me. how can we implement the same using groovy script to rename the interface name after importing?
Related Content
- 4 years ago
- 10 years ago
Recent Discussions
- 15 years ago