Lists Home |
Date Index |
- From: mark hu <email@example.com>
- To: David Orchard <firstname.lastname@example.org>, email@example.com
- Date: Tue, 15 Aug 2000 11:19:50 -0400
Here's some issues I think u can check out:
SOAP 1.1 ==>> The absence of the SOAP mustUnderstand attribute is
semantically equivalent to its presence with the value "0".
...... This attribute MUST appear in the instance in order to be effective
...... and since u import a schema and use element instance, looks like u
need to put this attribute back and about changing from uri-reference to
uriReference to enable xmlspy, I do not think it'll work - and I'll try the
same thing and see how it goes, cheers
"life is ..."
----- Original Message -----
From: David Orchard <firstname.lastname@example.org>
Sent: Monday, August 14, 2000 6:07 PM
Subject: SOAP and XML Schema validation?
> Apologies if this question has been answered before, an answer by
> would be as good as by value :-)
> My question is about the use of Schema validation of multiple namespaces,
> particular SOAP content on a server. I'm trying to create an extension on
> the SOAP Body element for my particular schema. Problem is, using
> base="tns:Body" for the complexType I'm creating doesn't seem to work.
> I have created an schema for the getLastTradePrice SOAP example, and I
> to extend the SOAP Body to specify my content.
> I tweaked the SOAP schema at http://schemas.xmlsoap.org/soap/envelope/ so
> that it would work in xmlspy, particularly: 1) change uri-reference to
> uriReference; 2) removed the default value for mustUnderstand
> The schema I created is:
> <schema targetNamespace="Some-URI"
> <import schemaLocation="../SOAPSchema.xsd"
> <element name="GetLastTradePrice" type="m:GetLastTradePriceType"/>
> <complexType name="GetLastTradePriceType" derivedBy="extension"
> base="tns:Body" >
> <element name="symbol" type="string"/>
> XML Spy says undefined value for 'base' encountered, yet tns:Body sure is
> My guess - to no surprise - is that it's a namespace issue, and I've
> some declaration. I think that the import of the SOAP schema should keep
> the full Qname for the soap elements and attributes. I tried removing
> import/namespace attribute, removing the xmlns:tns attribute, and adding
> xmlns:tns attribute to the complexType declaration.
> My 2nd guess is that it's a bug in xmlspy.
> Any help?
> Dave Orchard
> XML Architect
> Jamcracker, Inc.
> 935 Stewart Dr.
> Sunnyvale, CA 94086
> p: 408.830.1886
> f: 408.328.0936
> Named to Red Herring's list of 100 Most Important Companies:
> Named to Fortune's list of Cool Companies 2000: