Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft...

39
Copyright (c) 2009 innoQ Stefan Tilkov, innoQ Deutschland GmbH REST Introduction http://www.innoq.com

Transcript of Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft...

Page 1: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Stefan Tilkov, innoQ Deutschland GmbH

REST Introductionhttp://www.innoq.com

Page 2: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Stefan Tilkov

Geschäftsführer und Principal Consultant, innoQ Deutschland GmbH

Fokus auf SOA, Web-Services, REST

SOA-Editor InfoQ.com

Herausgeber “SOA-Expertenwissen”(mit Dr. Gernot Starke)

Mitglied JSR 311 EG

Autor “REST und HTTP”, dpunkt, Juli 2009

heise Developer podcast “SoftwareArchitekTOUR”(mit M. Stal, M. Völter, C. Weyer)

Page 3: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Beratungsunternehmen für Software-Architekturen

~50 Mitarbeiter in D (Ratingen, Darmstadt)und CH (Zürich)

Strategische IT-Beratung, Architekturconsulting, Entwicklung

Service-orientierte Architekturen (SOA)(WS-*, REST, OSS-Lösungen, Governance)

Rationelle Software-Produktion(MDA, MDSD, Java EE, Ruby on Rails)

Web Services Standards Overview

Vers

ion

3.0*

· Fe

brua

ry 2

007

This

post

er is

not

to b

e re

prod

uced

or t

rans

mitt

ed in

any

form

or f

or a

ny p

urpo

se w

ithou

t the

exp

ress

per

miss

ion

of in

noQ

Deut

schl

and

GmbH

.Co

pyrig

ht ©

inno

Q De

utsc

hlan

d Gm

bH.

All R

ight

s Res

erve

d. T

he p

oste

r may

also

con

tain

refe

renc

es to

oth

er c

ompa

ny, o

rgan

isatio

n, b

rand

and

pro

duct

nam

es.

Thes

e co

mpa

ny, o

rgan

isatio

n, b

rand

and

pro

duct

nam

es a

re u

sed

here

in fo

r ide

ntifi

catio

npur

pose

s onl

y an

d m

ay b

e th

e tr

adem

arks

of t

heir

resp

ectiv

e ow

ners

.

InteroperabilityIssues

Basic Profile1.1

WS-IFinal Specification

Basic Profile1.2

WS-IWorking Group Draft

Basic Profile2.0

WS-IWorking Group Draft

Basic Security Profile1.0

WS-IBoard Approval Draft

REL Token Profile1.0

WS-IWorking Group Draft

SAML Token Profile1.0

WS-IWorking Group Draft

Conformance Claim Attachment Mechanism

(CCAM)1.0

WS-IFinal Specification

Reliable AsynchronousMessaging Profile (RAMP)

1.0WS-I

Working Draft

Attachments Profile1.0

WS-IFinal Specification

Simple SOAPBinding Profile

1.0 · WS-IFinal Specification

Business Process ExecutionLanguage for Web Services 1.1(BPEL4WS) · 1.1 · BEA Systems, IBM,

Microsoft, SAP, Siebel SystemsOASIS-Standard

WS-Choreography ModelOverview1.0 · W3C

Working Draft

Web Service ChoreographyInterface (WSCI)

1.0 · W3CSun Microsystems, SAP, BEA Systems

and Intalio · Note

Business Process Specifications

Business Process ExecutionLanguage for Web Services 2.0

(BPEL4WS) · 2.0OASIS, BEA Systems, IBM, Microsoft,

SAP, Siebel Systems · Committee Draft

Business Process Management Language (BPML)

1.1BPMI.org

Final Draft

Web Service ChoreographyDescription Language (CDL4WS)

1.0W3C

Candidate Recommendation

XML Process Definition Language (XPDL)

2.0Final

WS-Policy1.5

W3CWorking Draft

WS-PolicyAssertions1.1

BEA Systems, IBM, Microsoft, SAP

Public Draft

Metadata Specifications

WS-PolicyAttachment1.2

W3CW3C Member Submission

WS-DiscoveryMicrosoft, BEA Systems, Canon,

Intel and webMethodsDraft

WS-MetadataExchange1.1

BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun

Microsystems and webMethodsPublic Draft

Universal Description,Discovery and Integration

(UDDI)3.0.2

OASISOASIS-Standard

Web Service DescriptionLanguage 2.0 SOAP Binding

2.0W3C · Working Draft

Web Service Description Language 2.0 Core

2.0W3C

Candidate Recommendation

Web Service DescriptionLanguage 1.1

1.1W3CNote

WS-Security1.1

OASISOASIS-Standard

WS-SecurityPolicy1.1

IBM, Microsoft, RSA Security, VeriSign

Public Draft

Security Specifications

WS-Security: SOAP Message Security

1.1OASIS

Public Review Draft

WS-Security: Username Token Profile

1.1OASIS

Public Review Draft

WS-Security:Kerberos Binding

1.0Microsoft, IBM, OASIS

Working Draft

WS-Federation1.0

IBM, Microsoft, BEA Systems, RSA Security, and VeriSign

Initial Draft

WS-Security: SAML Token Profile

1.1OASIS

Public Review Draft

WS-TrustBEA Systems, Computer Associates,

IBM, Layer 7 Technologies, Microsoft,Netegrity, Oblix, OpenNetwork, Ping

Identity Corp., Reactivity, RSASecurity, VeriSign and Westbridge

Technology · Initial Draft

WS-SecureConversationBEA Systems, Computer Associates,

IBM, Layer 7 Technologies, Microsoft,Netegrity, Oblix, OpenNetwork, Ping

Identity Corp., Reactivity, RSASecurity, VeriSign and Westbridge

Technology · Public Draft

WS-Security: X.509Certificate Token Profile

1.1OASIS

Public Review Draft

WS-ReliableMessaging1.1

OASISCommittee Draft

Reliability Specifications

WS-Reliable Messaging Policy Assertion (WS-RM Policy)

1.1OASIS

Committee Draft

WS-Reliability1.1

OASISOASIS-Standard

WS-Coordination1.1

OASISWorking Draft

WS-Business Activity1.1

OASISWorking Draft

WS-Atomic Transaction1.1

OASISCommittee Draft

WS-Composite ApplicationFramework (WS-CAF)

1.0 · ArjunaTechnologies, Fujitsu, IONA, Oracleand Sun Microsyst. · Committee Specification

WS-Context (WS-CTX)1.0 · Arjuna Technologies, Fujitsu,

IONA, Oracle and SunMicrosystems · Committee Draft

TransactionSpecifications

ResourceSpecifications

Management Using Web Services (WSDM-MUWS)

1.0OASIS

OASIS-Standard

Management Of Web Services (WSDM-MOWS)

1.0OASIS

OASIS-Standard

Management Specifications

WS-ManagementAMD, Dell, Intel, Microsoft and Sun

MicrosystemsPublished Specification

Service Modeling LanguageIBM, BEA, BMC, Cisco,

Dell, HP, Intel, Microsoft, SunDraft Specification

Web Services for Remote Portlets (WSRP)

2.0OASIS

Committee Draft

PresentationSpecifications

Web Services Resource Framework (WSRF)

1.2 · OASIS · OASIS-Standard

WS-BaseFaults (WSRF)1.2

OASISWorking Draft

WS-ServiceGroup (WSRF)1.2

OASISWorking Draft

WS-ResourceProperties1.2

OASISWorking Draft

WS-ResourceLifetime1.2

OASISWorking Draft

WS-TransferW3C

W3C Member Submission

Resource RepresentationSOAP Header Block (RRSHB)

W3C · Recommendation

WS-Coordination Framework (WS-CF)

1.0 · ArjunaTechnologies, Fujitsu, IONA, Oracleand Sun Microsystems · Committee Draft

WS-Transaction Management (WS-TXM)

1.0 · ArjunaTechnologies, Fujitsu, IONA, Oracleand Sun Microsystems · Committee Draft

innoQ Deutschland GmbH innoQ Schweiz GmbHHalskestraße 17 Gewerbestrasse 11D-40880 Ratingen CH-6330 ChamPhone +49 2102 77162-100 Phone +41 41 743 [email protected] · www.innoq.com

SOAP Message Transmission Optimization

Mechanism (MTOM)1.0 · W3C

Recommendation

SOAP1.2

W3CRecommendation

SOAP1.1

W3CNote

WS-Addressing – Core1.0

W3CRecommendation

WS-EventingW3C

Public Draft

WS-Addressing – WSDLBinding

1.0W3C

Candidate Recommendation

WS-Addressing – SOAP Binding

1.0W3C

Recommendation

WS-EnumerationSystinet, Microsoft, Sonic Software,

BEA Systems and Computer Associates

Public Draft

WS-Notification1.3

OASISOASIS-Standard

WS-BaseNotification1.3

OASISOASIS-Standard

WS-Topics1.3

OASISOASIS-Standard

WS-BrokeredNotification1.3

OASISOASIS-Standard

XML 1.11.1

W3CRecommendation

XML 1.01.0

W3CRecommendation

Namespaces in XML1.1

W3CRecommendation

XML Information Set1.0

W3CRecommendation

XML Schema1.1

W3CWorking Draft

XML binary Optimized Packaging (XOP)

1.0W3C

Recommendation

Describing Media Content ofBinary Data in XML (DMCBDX)

W3CNote

XML Specifications

Messaging Specifications SOAP

*HINWEIS: Dies ist eineim Informationsgehalt reduzierte Version des WS-Standards-Posters voninnoQ. Sie finden die Vollversion zum Downloadim PDF-Format unter:www.innoq.com/resources/ws-standards-poster/.Dort können Sie auch dasausgedruckte Poster imDIN A0 Format bestellen.

Page 4: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

What is REST?

Page 5: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

REST: An Architectural StyleOne of a number of “architectural styles”

... described by Roy Fielding in his dissertation

... defined via a set of constraints that have to be met

... architectural principles underlying HTTP, defined a posteriori

... with the Web as one particular instanceSee: http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm

Page 6: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

REST: The Web Used Correctly

A system or application architecture

... that uses HTTP, URI and other Web standards “correctly”

... is “on” the Web, not tunneled through it

... also called “WOA”, “ROA”, “RESTful HTTP”

Page 7: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

REST: XML without SOAP

Send plain XML (w/o a SOAP Envelope) via HTTP

... violating the Web as much as WS-*

... preferably use GET to invoke methods

... or tunnel everything through POST

... commonly called “POX”

Page 8: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Only option 1 is the right one

(because Roy said so)

Page 9: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

But we’ll go with option 2 (and equate “REST” with “RESTful HTTP usage”)

Page 10: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

and avoid option 3 like the plague

Page 11: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

REST Explainedin 5 Easy Steps

Page 12: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

1. Give Every “Thing” an ID

http://example.com/customers/1234

http://example.com/orders/2007/10/776654

http://example.com/products/4554

http://example.com/processes/sal-increase-234

Page 13: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

2. Link Things To Each Other

<order self=’http://example.com/orders/1234’> <amount>23</amount> <product ref=’http://example.com/products/4554’ /> <customer ref=’http://example.com/customers/1234’ /></order>

Page 14: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

3. Use Standard Methods

GET retrieve information, possibly cached

PUT Update or create with known ID

POST Create or append sub-resource

DELETE (Logically) remove

Page 15: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

4. Allow for Multiple “Representations”

GET /customers/1234Host: example.comAccept: application/vnd.mycompany.customer+xml

GET /customers/1234Host: example.comAccept: text/x-vcard

<customer>...</customer>

begin:vcard...end:vcard

Page 16: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

5. Communicate StatelesslyGET /customers/1234Host: example.comAccept: application/vnd.mycompany.customer+xml

time

<customer><order ref=’./orders/46’</customer>

GET /customers/1234/orders/46Host: example.comAccept: application/vnd.mycompany.order+xml

<order>...</order>

shutdownupdate softwarereplace hardwarestartup

Page 17: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Consequences

Page 18: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Page 19: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Mapping ExamplesgetFreeTimeSlots(Person) →GET /people/{id}/timeslots?state=free

rejectApplication(Application) →POST /rejections↵ <application>http://...</application>↵ <reason>Unsuitable for us!</reason>

performTariffCalculation(Data) →POST /contracts↵ Data←Location: http://.../contracts/4711→GET /contracts/4711/tariff←Result

shipOrder(ID) →PUT /orders/0815/status↵ <status>shipped</status>

shipOrder(ID) [variation] →POST /shipments↵ Data←Location: http://.../shipments/4711

Page 20: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

many very few(one per service)

many

Page 21: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

very few(fixed)

many

many

Page 22: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

REST and Web Services

Page 23: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Web Services Issues

Web Services are “Web” in name only

WS-* tends to ignore the web

Abstractions leak, anyway

Protocol independence is a bug, not a feature

Page 24: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

http://www.flickr.com/photos/stygiangloom/230412544/

Tunneling Through

POST

Page 25: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

POST http://example.com/CustomerMgmt<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <deleteCustomer xmlns="http://example.com/ns1"> <customerId>13</customerId> </ns:deleteCustomer> </soap:Body></soap:Envelope>

Method ID Endpoint

Page 26: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

“Endpoint”?

Page 27: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Page 28: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Page 29: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Web ServicesA separate interface (façade) for each purpose

As known CORBA, DCOM, RMI/EJB

Often used for SOA (“CORBA w/ angle brackets)

Application-specific protocol

+ getOrders()

+ submitOrder()

+ getOrderDetails()

+ getOrdersForCustomers()

+ updateOrder()

+ addOrderItem()

+ cancelOrder()

+ cancelAllOrders()

OrderManagementService

+ getCustomers()

+ addCustomer()

+ getCustomerDetails()

+ updateCustomer()

+ deleteCustomer()

+ deleteAllCustomers()

CustomerManagementService

Page 30: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Contribution to the Net’s Value

2 URLs

‣ http://example.com/customerservice‣ http://example.com/orderservice

1 method

‣ POST

Page 31: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

REST Approach

A single generic (uniform) interface for everything

Generic verbs mapped to resource semantics

A standard application protocol (e.g. HTTP)

GET - get order details

PUT - update order

POST - add item

DELETE - cancel order

/orders/{id}

GET - list all orders

PUT - unused

POST - add a new order

DELETE - cancel all orders

/orders

GET - get customer details

PUT - update customer

POST - unused

DELETE - delete customer

/customers/{id}

GET - list all customers

PUT - unused

POST - add new customer

DELETE - delete all customers

/customers

GET

PUT

POST

DELETE

«interface»

Resource

GET - get all orders for customer

PUT - unused

POST - add order

DELETE - cancel all customer orders

/customers/{id}/orders

Page 32: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Millions of URLs

‣ every customer‣ every order

4-6 supported methods per resource

‣ GET, PUT, POST, DELETE, OPTIONS, HEAD

Cacheable, addressable, linkable, ...

Contribution to the Net’s Value

Page 33: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Why You Should Care

Page 34: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Page 35: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

“My Internet is bigger than your enterprise.”

Page 36: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

We’ve been there before …

Page 37: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Page 38: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

VersicherungX

Unlock information as resources

Page 39: Stefan Tilkov, innoQ Deutschland GmbH REST Introduction · Intel and webMethods Draft WS-MetadataExchange 1.1 BEA Systems, Computer Associates, IBM, Microsoft, SAP, Sun Microsystems

Copyright (c) 2009 innoQ

Q&A

Stefan [email protected]://www.innoq.com/blog/st/Phone: +49 170 471 2625