correctly handle the case where a service is defined as using multiple bindings.  it is now possible, using ServiceProxy, to bind to a service that has the following wsdl definition:
correctly handle the case where a service is defined as using multiple
bindings.  it is now possible, using ServiceProxy, to bind to a service
that has the following wsdl definition:

<service name="foo">
  <port name="port-1" binding="ns1:Binding">
    <soap:address location="http://localhost:7001/server.py"/>
  </port>

  <port name="port-2" binding="ns2:Binding">
    <soap:address location="http://localhost:7001/server.py"/>
  </port>
</service>


this is important because it is now possible to implement multiple ports
using the same server, and access them through one unified WSDL (as opposed
to 1 wsdl for 1 port, a second wsdl for the second port, etc)


git-svn-id: c4afb4e777bcbfe9afa898413b708b5abcd43877@866 7150bf37-e60d-0410-b93f-83e91ef0e581

acigna/pywez,acigna/pywez,acigna/pywez