Sorry, but the extraDataType is a sequence of xsd:any and the code
generated by WSDL4J leaves me with a choice of how to encode the data.
It's okay to say that we have an agreement that the encoding will always
be "xml", but I'm afraid that the schema does not enforce this.
From: SRU (Search and Retrieve Via URL) Implementors
[mailto:[log in to unmask]] On Behalf Of Matthew J. Dovey
Sent: Friday, July 27, 2007 5:35 AM
To: [log in to unmask]
Subject: Re: No RecordPacking information in ScanRequest
The schemas do not permit a string value directly under
<extraResponseData> but expects child xml elements so
<extraResponseData>some string stuff</extraResponseData> should not
validate against the schemas
Will validate - what you stick under foo:myExtraStuff (string, XML,
mixed) is your own affair, and if you allow both string encoding or XML
underneath that, how you request that is also your own affair.
> -----Original Message-----
> From: SRU (Search and Retrieve Via URL) Implementors
> [mailto:[log in to unmask]] On Behalf Of Rob Sanderson
> Sent: 26 July 2007 17:15
> To: [log in to unmask]
> Subject: Re: No RecordPacking information in ScanRequest
> Isn't extraResponseData (etc) always returned as XML?
> On Thu, 2007-07-26 at 11:16 -0400, LeVan,Ralph wrote:
> > But, there is extraResponseData in a ScanResponse, and I need to
> > how to return that, as a string or as XML. Right now, I'm using the
> > default assumption that SRW returns strings and SRU returns XML, but
> > it seems like the client should have as much control over how
> > extraData is returned as they do over how records are returned.