- From: Arthur Ryman via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 06 Apr 2005 01:31:40 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/test-suite/documents/good/XsImport-2G In directory hutz:/tmp/cvs-serv15028/documents/good/XsImport-2G Added Files: reservationDetails.wsdl reservationItems.wsdl Log Message: Created test cases to illustrate use of <xs:import> with no schemaLocation when refering to inline schemas that have been encountered via <wsdl:import> and <wsdl:include> --- NEW FILE: reservationDetails.wsdl --- <?xml version="1.0" encoding="utf-8" ?> <description xmlns="http://www.w3.org/2004/08/wsdl" targetNamespace="http://greath.example.com/2004/services/retrieveDetails" xmlns:tns="http://greath.example.com/2004/services/retrieveDetails" xmlns:details="http://greath.example.com/2004/schemas/reservationDetails" xmlns:items="http://greath.example.com/2004/schemas/reservationItems" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2004/08/wsdl ../../../xmlcatalog/wsdl/wsdl20.xsd http://www.w3.org/2001/XMLSchema ../../../xmlcatalog/xsd/XMLSchema.xsd"> <documentation> Test case XsImport-2G shows that the schemaLocation attribute is not required when importing a namespace that is defined in an inline schema contained in an included WSDL document. In this example, the second inline schema imports the namespace defined in the inline schema that is contained in the included WSDL document, but does not specify a schemaLocation since the WSDL processor can locate it by virtue of it being contained the included WSDL document. </documentation> <include location="reservationItems.wsdl"/> <types> <xs:schema targetNamespace="http://greath.example.com/2004/schemas/reservationDetails"> <xs:import namespace="http://greath.example.com/2004/schemas/reservationItem" /> <xs:element name="reservationDetails"> <xs:complexType> <xs:sequence> <xs:element ref="items:confirmationNumber" /> <xs:element ref="items:checkInDate" /> <xs:element ref="items:checkOutDate" /> <xs:element ref="items:roomType" /> <xs:element ref="items:smoking" /> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> </types> <interface name="retrieveDetailsInterface"> <operation name="retrieve" pattern="http://www.w3.org/2004/03/wsdl/in-out"> <input messageLabel="In" element="#none" /> <output messageLabel="Out" element="details:reservationDetails" /> </operation> </interface> </description> --- NEW FILE: reservationItems.wsdl --- <?xml version="1.0" encoding="utf-8" ?> <description xmlns="http://www.w3.org/2004/08/wsdl" targetNamespace="http://greath.example.com/2004/services/retrieveDetails" xmlns:tns="http://greath.example.com/2004/services/retrieveDetails" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.w3.org/2004/08/wsdl ../../../xmlcatalog/wsdl/wsdl20.xsd http://www.w3.org/2001/XMLSchema ../../../xmlcatalog/xsd/XMLSchema.xsd"> <documentation> Test case XsImport-2G shows that the schemaLocation attribute is not required when importing a namespace that is defined in an inline schema contained in an included WSDL document. In this example, the second inline schema imports the namespace defined in the inline schema that is contained in the included WSDL document, but does not specify a schemaLocation since the WSDL processor can locate it by virtue of it being contained the included WSDL document. </documentation> <types> <xs:schema targetNamespace="http://greath.example.com/2004/schemas/reservationItems"> <xs:element name="confirmationNumber" type="string" /> <xs:element name="checkInDate" type="date" /> <xs:element name="checkOutDate" type="date" /> <xs:element name="roomType" type="string" /> <xs:element name="smoking" type="boolean" /> </xs:schema> </types> </description>
Received on Wednesday, 6 April 2005 01:31:41 UTC