Agenda 1.WSDL & XML Schema
Astronomicko-geofyzikálne observatórium, Modra An Order
Service 1: GetCustomerDetails Input: HTTP POST to Output: HTTP data returned CORP GOLD Fakulta matematiky, fyziky a informatiky UK Mlynská dolina, Bratislava OK
CustomerService operation: GetCustomerInformation Input: Output: CORP GOLD Fakulta matematiky, fyziky a informatiky UK Mlynská dolina, Bratislava OK
WSDL Web Services Description Language describes format of messages received and sent by the service –at abstract level (messages, operations, port types) –at concrete level (bindings, ports, services) optionally specifies also policies –e.g. “this service requires authentication done by WS- Security, specifically X.509 certificates” –specified in WS-PolicyAttachment
WSDL: abstract description interface (port type) consists of operations operation consists of messages –input, [output], [fault(s)] message consists of parts part is specified as an element or a type in XML Schema
CustomerService operation: GetCustomerInformation Input: Output: CORP GOLD Fakulta matematiky, fyziky a informatiky UK Mlynská dolina, Bratislava OK
... <wsdl:part name="CustomerInformation“ element="c:CustomerInformation"/>
XML Schema schema – a document that describes a set of compliant XML documents (instances of this schema) describes elements and their attributes (using types) types are: –simple (attributes and text-only elements) –complex (elements with subelements and/or attributes) simple types: –predefined –derived (e.g. by restriction) complex types are defined by: –attributes and/or subelements (list, cardinality, default values,...) –extension (≈ inheritance) –...
XML Schema (2) simple types examples string, normalizedString, token base64Binary hexBinary integer [non]positiveInteger [non]negativeInteger [unsigned][long|int|short|byte] decimal, float, double boolean dateTime, date, time duration gYear, gYearMonth, gMonth, gMonthDay, gDay Name QName NCName anyURI language ID, IDREF, IDREFS, ENTITY, ENTITIES, NOTATION, NMTOKEN, NMTOKENS
XML Schema (3) Nescafé 167 Jacobs 213
<xsd:schema elementFormDefault="qualified" targetNamespace=" xmlns:xsd="
WSDL: concrete description binding –specifies concrete protocol (SOAP 1.1, HTTP, MIME) –specifies details, e.g. for SOAP 1.1: how parts are mapped to SOAP Headers and/or SOAP Body call style: document or rpc encoding: literal or encoded transport (e.g. HTTP, SMTP, JMS) service –subelements port that specify physical addresses (e.g. URLs) at which individual bindings are reachable
<wsdl:binding name="SOAPBinding“ type="tns:GetCustomerInformationPortType"> <soap:binding style="document“ transport=" <soap:operation soapAction=" /> <wsdl:port name=“CustomerServicePort“ binding="tns:SOAPBinding"> <soap:address location="