> > Problem handling imports
> > Problem handling document/literal style
> > Failure to do the above means the toolkit isn't WS-I compliant!
> Yes, but that's an awful lot of toolkits.
> IMHO, as I've expressed in the past, it would be nice to have
> an official
> version of the WSDL (eg WS-I style) and 'contributed' WSDL
> files which can
> be used to generate exactly the same messages but work in less capable
It might be difficult to do a WSDL which avoided either.
Diagnostics and XCQL are in different namespaces (for sensible reasons)
which make it difficult to do in a single schema file - not impossible
but if the toolkit can't cope with imports it possible wo'n't cope with
the idioms you'd need to use to do this in a single file.
The XML on the wire for rpc/encoded is very different from the XML on
the wire for document/literal. You could with a bit of fiddling get a
WSDL which used rpc/literal and produced the same XML on the wire, but
even few toolkits support rpc/literal!