Web-Programmierung (WPR)

Size: px

Start display at page:

Download "Web-Programmierung (WPR)"

Oswald Baker
8 years ago
Views:

1 Web-Programmierung (WPR) Vorlesung X. Web Services Teil 2 mailto:wpr@gruner.org 1

2 21 Web Service World Wide Web seit Anfang 1990er Jahren Mensch Web-Browser Applikation HTTP XML over HTTP Web-Server Geschäftslogik (Business) Applikationszentriertes Web 2

3 21.1 Grundlagen Basisarchitektur Application Server Web-Service Client Discovery SOAP over HTTP Web-Server WSDL SOAP Web Services Subsystem Business- Komponente Business- Komponente Business- Komponente Business- Komponente UDDI- Registry Web-Container Container 3

Subsystem Business- Komponente Business- Komponente Business-

4 21.1 XML-RPC Remote Method Invocation via XML XML-RPC-Definition 4

5 21.1 XML-RPC Alternative XML-RPC <?xml version="1.0"?> <methodcall> <methodname>warenkorb.addposition </methodname> <params> <param> <value>monitor</value> </param> <param> <value><int>10</int></value> </param> </params> </methodcall> 5

6 21.1 XML-RPC XML-RPC Response <?xml version="1.0"?> <methodresponse> <fault><value><struct> <member> <name>faultcode</name> <value><int>4</int></value> </member> <member> <name>faultstring</name> <value><string>too many params. </string> </value> </member> </struct></value></fault> </methodresponse> 6

<value><int>4</int></value> </member> <member> <name>faultstring</name>

7 21.2 SOAP Simple Object Access Protocol (Alternative zu XML-RPC) Findet breite Unterstützung in Industrie IBM -> Apache -> Apache Axis Plattformunabhängig + XML-basiert W3C Standard seit 2000 (Version 1.1) SOAP-Spezifikation Message-Syntax Regeln für Codierung von Datentypen Aktuelle Version 1.2 ca. 60 Implementierungen (Stand 2004) 7

XML-basiert W3C Standard seit 2000 (Version 1.

8 21.2 SOAP 21.2 SOAP... <xsd:element name="envelope" type="tns:envelope"/> <xsd:complextype name="envelope"> <xsd:sequence> <xsd:element ref="tns:header" minoccurs="0"/> <xsd:element ref="tns:body" minoccurs="1"/> </xsd:sequence> </xsd:complextype>... 8

9 21.2 SOAP Nachrichtenformat SOAP Message SOAP-Envelope SOAP-Header SOAP-Body (RPC) Service Methode Parameter SOAP-Body DOCUMENT Beliebiges XML-Dokument 9

10 21.2 SOAP Beispiel: double getquote(string id); Request <soapenv:envelope...> <soapenv:body> <ns1:getquote xmlns:ns1= http... > <id xsi:type= xsd:string >401</id> </ns1> </soapenv:body> </soapenv:envelope> Missing Namespaces: xmlns:soapenv, xmlns:xsd, xmlns:xsi 10

.. > <id xsi:type= xsd:string >401</id> </ns1> </soapenv:body>

11 21.2 SOAP Beispiel: double getquote(string id); Response <soapenv:envelope...> <soapenv:body> <ns1:getquoteresponse xmlns:ns1=.. > <ns1:quotereturn xsi:type= xsd:double > 19.5</ns1:quoteReturn> </ns1:getquoteresponse> </soapenv:body> </soapenv:envelope> Missing Namespaces: xmlns:soapenv, xmlns:xsd, xmlns:xsi 11

. > <ns1:quotereturn xsi:type= xsd:double > 19.

12 21.2 SOAP Beispiel: double getquote(string id); Response (bei Fehler) <soapenv:envelope...> <soapenv:body> <soapenv:fault> <faultcode>server.error</faultcode> <faultstring>no such op.</faultstring> </soapenv:fault> </soapenv:body> </soapenv:envelope> Missing Namespaces: xmlns:soapenv, xmlns:xsd, xmlns:xsi 12

error</faultcode> <faultstring>no such op.

13 21.2 SOAP Transport HTTP, SMTP, FTP,... Auswahl => Binding HTTP-Übertragung HTTP-Request => SOAP-Request HTTP-Response => SOAP-Response 13

14 21.2 SOAP HTTP-Header SOAP Request POST /axis/services/vinoexchange HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, mulipartrelated, text/* Host: SOAPAction: Content-Length: 449 <?xml..> <soapenvelope>... </soapenvelope> 14

15 21.2 SOAP HTTP-Header SOAP Response HTTP/ OK Content-Type: text/xml; charset=utf-8 Date::... Server:Apache Coyote/1.0 Connection:close <?xml..> <soapenvelope>... </soapenvelope> 15

16 21.2 SOAP SOAP-Message mit Attachments SOAP Message MIME Header SOAP-Envelope SOAP-Header SOAP-Body SOAP-Part SOAP-Part 16

17 21.2 SOAP HTTP-Header SOAP Request POST /soap/servlet/messagerouter HTTP/1.0 Content-Type: mulitpart/related; boundary: ----=_Part_0_ ; SOAPAction: urn:vinoexchange:interest ----=_Part_0_ Content-Type: text/xml;charset=utf-8 <soapenvelope>... </soapenvelope> ----=_Part_0_ Content-Type:image/gif =_Part_0_

10269376 ; SOAPAction: urn:vinoexchange:interest ----=_Part_0_747212.

18 21.3 WSDL Web Service Description Language Öffentliche Methoden mit Signaturen Unterstützte Transport Protokolle Adresse des Web Services Typ-Schemata für den Datenaustausch => Schnittstellenbeschreibung (IDL) 18

Transport Protokolle Adresse des Web Services

19 21.3 WSDL <wsdl:definitions> <wsdl:types> <wsdl:message> <wsdl:porttype> <wsdl:binding> <wsdl:service> 19

20 21.3 WSDL <wsdl:definitions> wsdl:types <wsdl:types> <wsdl:message> <wsdl:porttype> <wsdl:binding> <wsdl:service> <wsdl:types> <xs:schema> <xs:element name="orderitem"> <xs:complextype> <xs:sequence> <xs:element ref="description"/> </xs:sequence> <xs:attribute name="amount" use="required" type="xs:integer"/> <xs:attribute name="orderid" use="required" type="xs:integer"/> </xs:complextype> </xs:element> </xs:schema> </wsdl:types> 20

<xs:element ref="description"/> </xs:sequence> <xs:attribute name="amount" use="required"

21 21.3 WSDL <wsdl:definitions> <wsdl:types> <wsdl:message> <wsdl:porttype> <wsdl:binding> <wsdl:service> wsdl:porttype abstrakte WebService Schnittstelle <wsdl:porttype name= CalculatePort > <wsdl:operation name= addvalue > <wsdl:input/> <wsdl:output/> </wsdl:operation> <wsdl:porttype> 21

22 21.3 WSDL wsdl:porttype Abstrakte Schnittstelle 1..n Operationenen Operation One-Way Request-Response Solicit-Response Notification Beschreibung Client sendet Nachricht ohne Response zu erwarten Client sendet Nachricht an Service und dieser reagiert mit Response Service sendet Nachricht anclient und bekommt von diesem eine Response Der W ebservice sendet Nachricht an den Client 22

23 21.3 WSDL <wsdl:definitions> wsdl:message (Nachrichten) <wsdl:types> <wsdl:message> <wsdl:porttype> <wsdl:message name= getquotereq > <wsdl:part name= id type= xsd:string /> </wsdl:message> <wsdl:binding> <wsdl:service> 23

24 21.3 WSDL <wsdl:definitions> <wsdl:types> <wsdl:message> <wsdl:porttype> <wsdl:binding> <wsdl:service> wsdl:binding Bindung an Protokoll Nachrichtenprotokoll <wsdl:binding name= CalculatePort > <wsdl:soapbinding style= rpc transport= > <wsdl:operation> </wsdl:operation> </wsdl:soapbinding> <wsdl:binding> 24

25 21.3 WSDL <wsdl:definitions> wsdl:service 1..n -> Port <wsdl:types> <wsdl:message> <wsdl:porttype> <wsdl:binding> <wsdl:service name= CalculateService > <wsdl:port name= > <wsdl:address location= > </wsdl:address> </wsdl:port> <wsdl:service> <wsdl:service> 25

26 21.3 WSDL <wsdl:definitions> <wsdl:types> <wsdl:message> <wsdl:porttype> <wsdl:binding> wsdl:definitions (Namensräume) <wsdl:definitions xmlns:wsdl=... targetnamespace=... xmlns:wsdlsoap=... xmlns:soapenc=... <wsdl:service> > </wsdl:definitions> 26

27 21.3 WSDL Developing a Web Service? How? Where to start? 27

Joke Server example. with Java and Axis. Web services with Axis SOAP, WSDL, UDDI. Joke Metaservice Joke Server Joke Client.

Joke Server example. with Java and Axis. Web services with Axis SOAP, WSDL, UDDI. Joke Metaservice Joke Server Joke Client. Joke Server example SOAP and WSDL with Java and Axis Interactive web services, Course, Fall 2003 Henning Niss Joke Metaservice Joke Server Joke Client 3 meta service 2 IT University of Copenhagen client