Date:Tue, 20 Nov 2001 10:04:52 -0000
Reply-To:"Z39.50 Next-Generation Initiative" <[log in to unmask]>
Sender:"Z39.50 Next-Generation Initiative" <[log in to unmask]>
From:Matthew Dovey <[log in to unmask]>
Subject:Re: No response from your server
Comments:To: [log in to unmask]Content-Type:text/plain; charset="us-ascii"
But this breaks one of *your* claimed motivations - namely the use of
existing SOAP toolkits etc.
The typical user of a SOAP toolkit would expect the deserialiser to
convert the over the wire XML to the parameters of their RPC
operation/method/function (terminology depending on their choice of
computer language) *and* the serialiser to handle the conversion of
their response to the XML. They probably would never get their hands
dirty by looking at the low level XML. (In much the same way most Z39.50
programmers rely on a BER toolkit rather than jump in and deal with the
BER directly).
However, to handle the extensible response format you are now proposing
that the programmer doesn't use the SOAP toolkit to serialise the
response but builds the XML directly - so they now have to start dealing
with DOMs etc. (which I suspect some will regard as low level difficult
stuff ;-) ). Given how simple our request XML is, there seems little
point in using the SOAP deserialiser, if already have had to tackle DOMs
etc so very little point (and quite a bit of overhead) in using a SOAP
toolkit at all.
So yes we can do this, but we are moving away from our original goals.
Matthew
> -----Original Message-----
> From: LeVan,Ralph [mailto:[log in to unmask]]
> Sent: 19 November 2001 17:34
> To: [log in to unmask]
> Subject: Re: No response from your server
>
> It would definitely be an extension, but that won't help for
> serializer/deserializer classes. I'm pretty sure we'll have to stick
to
> string as the official response and explain the content through the
> documentation.
>
> Ralph
>
> > -----Original Message-----
> > From: Matthew Dovey [mailto:[log in to unmask]]
> > Sent: Monday, November 19, 2001 11:49 AM
> > To: [log in to unmask]
> > Subject: Re: No response from your server
> >
> >
> > Is seems a bit of a hack though...
> >
> > I'll take another look. Are we agreed that an alternative
> > response would
> > be an extension of what I call RS_1 rather than an totally different
> > schema? (with the possible exception of the Explain schema).
> > It might be
> > possible to put a stronger typing to the response, which I'd
prefer...
> >
> > Matthew
> >
> > > -----Original Message-----
> > > From: LeVan,Ralph [mailto:[log in to unmask]]
> > > Sent: 19 November 2001 13:30
> > > To: [log in to unmask]
> > > Subject: Re: No response from your server
> > >
> > > Can't we just correct the WSDL to specify that the response
> > object is
> > a
> > > string?
> > >
> > > Ralph
> > >
> > > > -----Original Message-----
> > > > From: Matthew Dovey [mailto:[log in to unmask]]
> > > > Sent: Monday, November 19, 2001 8:28 AM
> > > > To: [log in to unmask]
> > > > Subject: Re: No response from your server
> > > >
> > > >
> > > > Correct.
> > > >
> > > > I did warn people of this at the meeting back in
> > June/July, that the
> > > > proposed mechanism for specifying a response schema in the
> > > > request would
> > > >
> > > > prevent cause us incompatibilities with WSDL and also
> > SOAP toolkits.
> > > >
> > > > Matthew
> > > >
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: LeVan,Ralph [mailto:[log in to unmask]]
> > > > > Sent: 19 November 2001 12:38
> > > > > To: [log in to unmask]
> > > > > Subject: Re: No response from your server
> > > > >
> > > > > So, if I read this correctly, you have defined your
> > searchRetrieve
> > > > method
> > > > > as
> > > > > returning an object of type searchRetrieveResponse. I
> > defined by
> > > > > searchRetrieve method as returning a string. I suspect
> > that your
> > > > response
> > > > > is correct as far as the WSDL is concerned. But, I believe
the
> > WSDL
> > > > is in
> > > > > error as far as the extensibility claims for our prototype are
> > > > concerned.
> > > > >
> > > > > If we are to return a well-known structured object,
> > then there is
> > no
> > > > > extensibility mechanism. There is no point in have a
> > responseSchema
> > > > in
> > > > > the
> > > > > request if the object that we are returning cannot
> > carry the data
> > > > required
> > > > > for the response. The only way we can vary our
> > response with the
> > > > > responseSchema is if we return a simple string and embed an
XML
> > > > document
> > > > > in
> > > > > the string.
> > > > >
> > > > > Isn't that correct?
> > > > >
> > > > > Ralph
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: [log in to unmask] [mailto:[log in to unmask]]
> > > > > > Sent: Sunday, November 18, 2001 11:06 PM
> > > > > > To: LeVan,Ralph
> > > > > > Subject: Re: No response from your server
> > > > > >
> > > > > >
> > > > > > On Tue, Nov 06, 2001 at 08:05:50AM -0500, LeVan,Ralph wrote:
> > > > > > > Some progress. Now I get this error:
> > > > > > >
> > > > > > > SOAPException=[SOAPException: faultCode=SOAP-ENV:Client;
> > > > > > msg=No Deserializer
> > > > > > > found to deserialize a
> > > > > > 'urn:z3950:ZNG_Prototype1:searchRetrieveResponse'
> > > > > > > using encoding style
> > > > 'http://schemas.xmlsoap.org/soap/encoding/'.;
> > > > > > > targetException=java.lang.IllegalArgumentException: No
> > > > > > Deserializer found to
> > > > > > > deserialize a
> > > > > > 'urn:z3950:ZNG_Prototype1:searchRetrieveResponse' using
> > > > > > > encoding style
'http://schemas.xmlsoap.org/soap/encoding/.]
> > > > > > >
> > > > > > > I defined my server as returning a String and put the XML
> > > > > > document in it.
> > > > > > > It looks like you are returning an object of type
> > > > > > searchRetrieveResponse.
> > > > > > >
> > > > > > > Got a guess as to which one is right? If it's you, then
> > > > > > what do I have to
> > > > > > > do to get the message deserialized?
> > > > > > >
> > > > > > > Ralph
> > > > > >
> > > > > > I just came across this old email. It looks like my
> > recent mail
> > is
> > > > > > actually something we started talking about previously.
> > > > > >
> > > > > > Here is a working search/retreive conversation between my
> > > > client and
> > > > > > server. This does not mean its correct. It just means its
> > > > consistent
> > > > > > with itself.
> > > > > >
> > > > > > HTTP REQUEST:
> > > > > >
> > > > > > POST /z3950.simdb.com/Marc HTTP/1.1
> > > > > > SOAPAction: ""
> > > > > > Content-Type: text/xml; charset=UTF-8
> > > > > > Content-Length: 707
> > > > > > User-Agent: SIM Soap Client 0.01
> > > > > > Host: z3950.simdb.com:6745
> > > > > >
> > > > > > <?xml version="1.0"?>
> > > > > > <SOAP-ENV:Envelope
> > > > > >
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encodi
> > > > > > ng/"
> > > > > > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> > > > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> > > > > > xmlns:ns0="http://www.w3.org/1999/XMLSchema"
> > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> > > > > > <SOAP-ENV:Body>
> > > > > > <m:searchRetrieve xmlns:m="urn:z3950:ZNG_Prototype1"><query
> > > > > > xsi:type="ns0:string">title=smith</query><startRecord
> > > > > > xsi:type="ns0:int">1</startRecord><maximumRecords
> > > > > > xsi:type="ns0:int">1</maximumRecords><responseSchema
> > > > > > xsi:nil="true"/><recordSchema
> > > > > > xsi:nil="true"/></m:searchRetrieve></SOAP-ENV:Body>
> > > > > > </SOAP-ENV:Envelope>
> > > > > >
> > > > > >
> > > > > > HTTP RESPONSE:
> > > > > >
> > > > > > HTTP/1.1 200
> > > > > > Accept-Ranges: bytes
> > > > > > Content-Length: 1593
> > > > > > Content-Type: text/xml
> > > > > > Date: Mon, 19 Nov 2001 04:04:38 GMT
> > > > > > Server: simwebs/3.1.9
> > > > > >
> > > > > > <?xml version="1.0"?>
> > > > > > <SOAP-ENV:Envelope
> > > > > >
> > > >
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
> > > > > >
> > > > > > xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
> > > > > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> > > > > > xmlns:ns0="http://www.w3.org/1999/XMLSchema"
> > > > > > xmlns:ns1="urn:z3950:ZNG_Prototype1"
> > > > > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> > > > > > <SOAP-ENV:Body>
> > > > > > <m:searchRetrieveResponse
> > > > > > xmlns:m="urn:z3950:ZNG_Prototype1"><return
> > > > > > xsi:type="ns1:searchRetrieveResponse"><resultSetReference
> > > > > > xsi:type="ns1:resultSetReference"><resultSetName
> > > > > > xsi:type="xsd:string">default</resultSetName><resultSetTTL
> > > > > >
xsi:type="xsd:duration">P0DT00H05M00S</resultSetTTL></resultSe
> > > > > > tReference><totalHits
> > > > > > xsi:type="xsd:int">1</totalHits><records
> > > > > > xsi:type="SOAP-ENC:Array"
> > > > > > SOAP-ENC:arrayType="ns1:record[1]"><record
> > > > > > xsi:type="ns1:record"><schema
> > > > > > xsi:type="xsd:string">SUTRS</schema><recordData
> > > > > > xsi:type="xsd:string">MARC:
> > > > > >
> > > > > > 041 0 a eng
> > > > > > 100 1 a Bierce, Ambrose
> > > > > > d 1842-1914?
> > > > > > 245 00 a Can such things be
> > > > > > 260 b Johnathan Cape and Harrison Smith
> > > > > > c 1909
> > > > > > 440 a Internet Wiretap Edition
> > > > > > 856 s 339k
> > > > > > u
> > > > > > gopher://wiretap.spies.com:70/00/Library/Classic/cansuch.txt
> > > > > > 956 b 1909
> > > > > > 958 a Crowley, Rebecca
> > > > > > b [log in to unmask]
> > > > > > 959 a Fiction
> > > > > > </recordData></record></records><status
> > > > > > xsi:type="ns1:status"><statusCode
> > > > > > xsi:type="xsd:int">0</statusCode><diagnostic xsi:nil="true"
> > > > > > xsi:null="1"/></status></return></m:searchRetrieveResponse>
> > > > > > </SOAP-ENV:Body>
> > > > > > </SOAP-ENV:Envelope>
> > > > > >
> > > >
> >
