Forum Discussion
16 years ago
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.
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.
Related Content
- 4 years ago
- 10 years ago
Recent Discussions
- 15 years ago