> Why do we point to the srw-bindings.wsdl on the SRW
> specifications page and
> not the srw-service.wsdl? I ask this because I've just spent
> the last two
> days tracking down a problem caused by this.
Errm, because srw-service.wsdl defines a particular instance of a SRW
WebService, whereas srw-bindings.wsdl defines all of the non-instance
specific stuff. In particular it specifies the actual URL of the SRW
WebService (the active bit of the code is)
<port name="SearchRetrieveService" binding="SRW:SRW-SoapBinding">
<soap:address location="http://your-url-here/" />
srw-bindings.wsdl on the other hand specified all of the SRW stuff apart
from the instance details.
What you are supposed to do is write a WSDL for you SRW instance, import
srw-bindings.wsdl, and write the <wsdl:service> part for your particular
SRW service including your particular URL end point.
srw.services.wsdl is just an example/template of what your wsdl should
look like (you should change http://your-url-here/ to something
> Also, was there a warning sent out when the latest wsdl was
> moved to LC?
> Like I said, the new WSDL generates objects with different
> names, so I had
> to change my implementation code.
"New WSDL"? - the WSDL hasn't changed since last December. There were a
lot of e-mails from November from me asking about URL's and Namespaces
etc. and one in which I sent the ones I had decided to stick with (in
case there were any objections).