Matthew J. Dovey wrote:
>I've been using XMLSpy to validate the schemas plus trying them in the
>Axis and .Net SOAP toolkits!
>It does appear that this is a problem with the schema though. I switched
>from xsd:sequence to xsd:all to accommodate a request from Ralph for a
>base request and response types. Using all, I'd hoped to avoid having to
>change any implied order to the parameters listed in the specification
>document (see Ralph's e-mail of the 23 Jan "Based Message Type", and
>mine of the 26 Jan "Re: Review of 1.1"). I did ask at the time "I've
>changed this to xsd:all i.e. order is no longer important - this may
>break things (I've checked that Axis can cope), so comments/reactions
>please!!" but got no reactions or comments (or at least didn't spot
>XMLSpy and the other tools I was using seemed happy with this approach,
>but it appears this is wrong see
>Sorry, Ray, I'll have to post another update to the schema.
So it looks like that I struck a mine in the schema. May I kindly ask
what your time horizon is for updating the schema ??
Any help needed ??
Marc Cromme, Indexdata