The bindingId in the server endpoint of the hello_world sample is
http://schemas.xmlsoap.org/soap/ whereas in the endpoint of the ws_rm
demo it is http://schemas.xmlsoap.org/wsdl/soap/.
Both samples use wsdl first, and both wsdls have the same
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";>
element attached to their <wsdl:binding> element.
At the moment, this causes problems for RM when it builds up the service
model for the RM endpoint based on the service model for the application
endpoint.
In one case, it succeeds in creating a SoapBindingInfo, in the other it
throws an exception because the soap version cannot be determined from
bindingId http://schemas.xmlsoap.org/soap/.
I can work around it by using the constructor for SoapBindingInfo that
takes the SoapVersion as an argument, but find the behaviour a bit strange.
Why do the two endpoints end up with different bindingIds in the first
place?
Andrea.
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
