You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by John WILSON <jw...@yahoo.fr> on 2001/04/11 09:15:39 UTC
SOAP Quizz
Hi There,
Let us say I want to create an order. I using soap to
send in my order request that looks like this:
1 OrderBrief Object made up of:
* 1 Delivery Address (VODeliveryAddress)
* n Article Orders (VOOrderLines)
SOAP generates a very nice message for me:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:createOrder xmlns:ns1="urn:OrderManager"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<VOOrderBrief xmlns:ns2="urn:xml-soap-order-demo"
xsi:type="ns2:voorderbrief">
<paymentMode xsi:type="xsd:string">787</paymentMode>
<customerNo xsi:type="xsd:int">831</customerNo>
<freightCost
xsi:type="xsd:double">0.1922546863392245</freightCost>
<deliveryDate
xsi:type="xsd:timeInstant">2001-03-15T17:53:25Z</deliveryDate>
<status xsi:type="xsd:string">201</status>
<VODeliveryAddress xsi:type="ns2:voaddress">
<city xsi:type="xsd:string">794</city>
<state xsi:type="xsd:string">831</state>
<zipCode xsi:type="xsd:string">403</zipCode>
<street xsi:type="xsd:string">427</street>
<name xsi:type="xsd:string">787</name>
</VODeliveryAddress>
<VOOrderLines
xmlns:ns3="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns3:Array" ns3:arrayType="xsd:ur-type[28]">
<item xsi:type="ns2:voorderline">
<quantity xsi:type="xsd:int">794</quantity>
<articleName
xsi:type="xsd:string">403</articleName>
<deliveryDate
xsi:type="xsd:timeInstant">2001-03-15T17:53:25Z</deliveryDate>
<articleNo xsi:type="xsd:string">427</articleNo>
</item>
<item xsi:type="ns2:voorderline">
<quantity xsi:type="xsd:int">794</quantity>
<articleName
xsi:type="xsd:string">403</articleName>
<deliveryDate
xsi:type="xsd:timeInstant">2001-03-15T17:53:25Z</deliveryDate>
<articleNo xsi:type="xsd:string">427</articleNo>
</item>
<item xsi:type="ns2:voorderline">
<quantity xsi:type="xsd:int">794</quantity>
<articleName
xsi:type="xsd:string">403</articleName>
<deliveryDate
xsi:type="xsd:timeInstant">2001-03-15T17:53:25Z</deliveryDate>
<articleNo xsi:type="xsd:string">427</articleNo>
</item>
</VOOrderLines>
</VOOrderBrief>
</ns1:createOrder>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Ok, it's a bit long...
Now when vaidating my order on the server side, I find
out that the zip code of the delivery address is not
quite correct, and that the last item I wish to
purchase does not have a valid article number...
What do you think the answer should be???
I would very much like to have a list of all the
errors in my order to correct them in one go.
This you may say is application specific... Probably
so , but you will soon enough find out that you will
be having very similar problems and shouldn't this be
standardized?
It is a nice thing to send objects on the network in a
standardized manner but it is also necessary to tell
the guy sending the object on the network what is
wrong with his object...
Is there a standard for this kind of error handling...
Cheers and thanks
___________________________________________________________
Do You Yahoo!? -- Pour dialoguer en direct avec vos amis,
Yahoo! Messenger : http://fr.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org