>> the code produced from the WSDL by Mono leaves a lot to be desired (eg
>> everything is a string),
> Is that an issue with Mono or the WSDL?
I have no idea.
I can't compile the current stuff in place, but if I download it all it
Resulting c# code is at:
>> Hence, my suggestion to have an official WS-I WSDL and some
>> 'this should do the trick' WSDLs.
> We could move all the imports into a single file - which might help in
> certain cases. Moving xcql into the same URL folder as the other schemas
> might also help!
It at least wouldn't hurt.
> However a WSDL file which did RPC/Encoded could produce a SRW
> implementation which would not interoperate with a Doc/Literal SRW
> (since it might use SOAP:Arrays etc.) so would be highly toolkit
> dependent and may often require additional tweaking of the toolkit.
Right. But the code produced -can- be tweaked. A page with a how-to for
tested tks plus the WSDL used would go a long way, IMO.
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. University of Liverpool
I L L U M I N A T I L5R Shop: http://www.cardsnotwords.com/