Add support for multi-service and multi-port binding WSDL files

[smokhov]

• Closes fix: serviceName and portName must correspond to port binding #1226

This PR supersedes PR #1226 (by @paulish). For now simply sync'ing it with master. Unsure yet what type of test it would have... It seems covered? But I don't have a concrete example in mind.

[w666]

Will have a look in this one later. It is in my backlog.

[w666]

Will have a look in this one later. It is in my backlog.

fyi: I am working on a test for this one when have time, but due to other issues in this project this is not a first priority.

[w666]

Was looking into this past week. Still not sure I understand the problem because I managed to create a WSDL file that breaks it.
Basically, when there are two services and port bindings are in order of appearance it works, but once I change, for example, port order it breaks parsing. I assume this is what this PR was about. But it does not work, moreover it works same way before the fix.

Anyway, I continue investigating this. At least I have a good WSDL and a template for a test.

[w666]

Reverted original change, I think it is not correct, moreover it does not fix anything. Instead fixed looked through service->port bindings. Added new multi-service/multi-port WSDL and new tests.

@smokhov would you be able to review this, in case I overlooked something?

[smokhov]

Reverted original change, I think it is not correct, moreover it does not fix anything. Instead fixed looked through service->port bindings. Added new multi-service/multi-port WSDL and new tests.

@smokhov would you be able to review this, in case I overlooked something?

I had a look at the changes, you've done quite a comprehensive test coverage for the issue, so I think it's good to go. I guess the code has improved since the times of the original PR so the original change became redundant, but it's nice now to have it fully covered as well.