Matthew J. Dovey wrote:
> No - the namespaces are correct. If you made the changes suggested, WSDL
> compilers would break because srw-bindings.wsdl has the entry
OK. My bad. Messing a location with a namespace. Again:-)
>
> targetNamespace="http://www.loc.gov/zing/srw/srw-bindings/
>
> What you've illustrated is that wget is not handling namespace location
> correctly
wget handles fetching web resources just fine. It reports an error when
given an incorrect URL. So don't blame it on good old wget. It's my bad.
I might have given this information before. But the procedure to publish
any SRW SOAP WSDL for a service (I'm sure you'll correct me if I'm
wrong) is to copy all the WSDL/XSDs etc files from the LoC server, since
the sample server WSDL refer to srw-bindings.wsdl, which in turns points
to the types.. etc. And the location is the same as the sample service.
If there was a way to just get the sample service (point to the "common"
files on the Loc Server) - that would have been convenient.
> location="srw-bindings.wsdl" means that srw-bindings.wsdl should be
> accessed from the same location as the file
> http://www.loc.gov/z3950/agency/zing/srw/srw-sample-service.wsdl i.e.
> http://www.loc.gov/z3950/agency/zing/srw/
>
> XML namespace aware tools such as XMLSpy, Axis WSDL2Java, .Net WSDL
> compiler (which people using SOAP) etc. know this and the files will
> work correctly as is - this is proved since
> http://www.ceridwen.com/srw/schema/wsvn/SRW%201.1%20Schema/skeleton-impl
> ementations/?rev=0&sc=0 contains code generated automatically from the
> schemas stored at ceridwen.com using Axis and Mono (mainly to catch
> silly mistakes).
>
> What you've illustrated is that there aren't many people using wget
> (which isn't a SOAP tool, nor to my knowledge SOAP aware) to try and
> download the schemas.
Right. It's just too complicated for regular people to figure out what
the right URL, to give to wget, would be.
/ Adam
>
> Matthew
>
>
>>-----Original Message-----
>>From: SRU (Search and Retrieve Via URL) Implementors
>>[mailto:[log in to unmask]] On Behalf Of Adam Dickmeiss
>>Sent: 15 November 2005 13:53
>>To: [log in to unmask]
>>Subject: Incorrect namespace import in sample service WSDLs
>>
>>Rikke Lose from DBC has notified me about problems with the
>>SRW sample WSDL. Actually there is a similar problem with the
>>SRU sample.
>>
>>In
>> http://www.loc.gov/z3950/agency/zing/srw/srw-sample-service.wsdl
>>we have:
>><import namespace="http://www.loc.gov/zing/srw/srw-bindings/"
>>location="srw-bindings.wsdl"/>
>>
>>With wget:
>>adam@peanut:~$ wget
>>http://www.loc.gov/zing/srw/srw-bindings/srw-bindings.wsdl
>>--14:50:07--
>>http://www.loc.gov/zing/srw/srw-bindings/srw-bindings.wsdl
>> => `srw-bindings.wsdl'
>>Resolving www.loc.gov... 140.147.249.7
>>Connecting to www.loc.gov|140.147.249.7|:80... connected.
>>HTTP request sent, awaiting response... 301 Moved Permanently
>>Location:
>>http://www.loc.gov/z3950/agency/zing/srw/srw-bindings/srw-bind
>>ings.wsdl
>>[following]
>>--14:50:08--
>>http://www.loc.gov/z3950/agency/zing/srw/srw-bindings/srw-bind
>>ings.wsdl
>> => `srw-bindings.wsdl'
>>Connecting to www.loc.gov|140.147.249.7|:80... connected.
>>HTTP request sent, awaiting response... 404 Not Found
>>14:50:09 ERROR 404: Not Found.
>>
>>It does not resolve. It should be
>>namespace="http://www.loc.gov/z3950/agency/zing/srw/"
>>
>>In
>> http://www.loc.gov/z3950/agency/zing/srw/sru-sample-service.wsdl
>>we have:
>><import namespace="http://www.loc.gov/zing/srw/sru-bindings/"
>>location="sru-bindings.wsdl"/>
>>
>>It does not resolve. It should be
>>namespace="http://www.loc.gov/z3950/agency/zing/srw/"
>>
>>The draft schemas at the http://www.ceridwen.com the same problem.
>>
>>If this problem has persisted for a long time it shows that
>>people don't report bugs or that only few deploy SRW (SOAP).
>>
>>/ Adam
>
>
>
|