Adding multiple WSDLs with same interface name

Question

Hi,I have 3 WSDL URLs to be added in a project and used for running various tests.ex:&nbsp; http://servername:8080/pwd/Interface1?wsdl&nbsp; &nbsp; &nbsp;  http://servername:8080/abc/Interface1?wsdl&nbsp; &nbsp; &nbsp;  http://servername:8080/jkl/Interface1?wsdlI observe that since the interface names are same in all the 3 urls, the definitions get overwritten each time and the existing methods obviously gets replaced depending upon the new URL.The workaround I used is to create a dummy project, add a WSDL and then clone the interface into the main project. I repeat this for the other 2 urls and I get 3 treeviews with the caption "Interface1Binding" for the parent node. Each tree view displays the methods under relevant URLs.Is there any other workaround?RegardsSandeep

karelhusa · Answer

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")&nbsp;
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")&nbsp;
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.
&nbsp;
This approach is especially helpful when you need to test or mock multiple versions of the same service within the same SoapUI project.
&nbsp;
Best regards,
Karel
&nbsp;

scr · Answer

I'm not sure I understand your problem... can you elucidate? Maybe I just don't have the experience needed to understand what you are trying to do...

astanley · Answer

I have the same problem. I am using the same wsdl:binding/@name attribute for different web services. When I add a WSDL to a project that already has an interface of the same name, soapUI complains "Interface [xxxxxx] already exists in project, update instead?". If I say no, the new interface is not added, if I say yes the new interface is added and replaces the existing one. What I want is for both interfaces to be in the project, even though they have the same name.

I use the same workaround as snsandeep, but it would be better if I could add the WSDL directly to the existing project without having to use a dummy project.

snsandeep · Answer

Hi SCR,If you try to add 2 WSDL URLs with the same interface name as I have mentioned in the hypothetical example I have given, the methods of the second URL I add replaces the methods of the firts URL. Just try thiis workflow and you will know.RegardsSandeep

smartbear_suppo · Answer

Hello,Sadly, this is a limitation of soapUI. You will have to continue using these workarounds for now. Sorry for the inconvenience.Regards,Daineviware.com

Forum Discussion

Adding multiple WSDLs with same interface name

9 Replies

Related Content

Adding Multiple Monitors at once

Operating with REST Interfaces and Requests

Same interface/wsdl is added twice in soap project

ERROR:org.apache.xmlbeans.impl.values.XmlValueDisconnectedException when updating interface

OpenJDK Multiple Vulnerabilities

Recent Discussions

clone TestSuite fails when there are more project with the same name

Will SOAP UI 5.6.1 work with JDK 8

SOAP Request works in SoapUI, but not in C# code

How to configure Swagger in Paas to use it in Oracle APEX instance.

log4j1.x vulnerability