Hi Dies,
Thank you for your reply.
So we can say the mapping from port to address is one-to-one, if multiple ports correspond to the same binding, that means they are simply alternative addresses for the same service implementation. So they are just backup addresses for each other, right? So it is at client program's discretion to choose a port. If YourServicePortA is chosen, SOAPEnvelope is routed to localhost, if YourServicePortB is chosen, the SOAPEnvelope is routed to differenthos. Correct? It seems that this situation is just to provide a way for two deployments of the same service on different machines to share WSDL.
Regards,
Xinjun
On 4/19/06, Dies Koper <[EMAIL PROTECTED]> wrote:
Hello Xinjun,
Multiple ports can map to one binding. I.e. you make the same service
available through different URLs.
<wsdl:service name="YourService">
<wsdl:port binding="impl:YourSoapBinding" name="YourServicePortA">
<wsdlsoap:address
location=" http://localhost/yourmodule/services/port_a"/>
</wsdl:port>
<wsdl:port binding="impl:YourSoapBinding" name="YourServicePortB">
<wsdlsoap:address
location=" https://differenthost/yourmodule/webservices/port_b"/>
</wsdl:port>
</wsdl:service>
Regards,
Dies
Xinjun Chen wrote:
> In WSDL we may have multiple bindings for a single portType. Every service
> may have multiple ports.
> Is the mapping from port to binding is one to one?
>
> Regards,
> Xinjun
