#166 Alternative interface labelling

[Anonymous]

In our EAI architecture we have a lot of one operation wsdl files which are grouped together in one component. The wsdl's are generated from the middleware service definitions.

One 'component' has a number of services thus a number of one operation wsdl's. Unfortunately the generated wsdl's (runtime) all have the same portname and bindingname, which we cannot influence.

Hence adding more then one wsdl to a SoapUI project is not possible.

I therefore would like the option to define the interface name when adding a new wsdl to the project instead of taking the binding name/port name.

Regards,

Wilco

[Jesper Goertz]

Logged In: YES
user_id=1305887
Originator: NO

we have the same problem with some services having the same binding respectively port name, which means we cannot have them in the same project and cannot make test suites using all needed services.

If binding name differs from port name you can change soapui preferences / WSDL Settings / Name with Binding, and be able to use two service interfaces with same binding (or port) name in a project.

It should be possible to specify the name or rename the interface.