Download presentation
Presentation is loading. Please wait.
Published byRoss Shepherd Modified over 9 years ago
1
Web services sub-team report CPPA June ’02 F2F Reston, Virginia.
2
Agenda Scope of the project Current sub-team WSDL overview CPA -> WSDL element mapping Rosettanet PIP3A4 example Open issues
3
Scope of the project Research how CPPA information can be integrated with following WS specifications* Web services description standard (WSDL) Web service messaging standard/s (SOAP, SOAP + WS Routing + WS Security, etc.) Web services choreography standard/s (IBM WSFL, MS XLANG, etc.) *in order of maturity/priority
4
Current sub-team Arvola Chan Dale Moberg Marty Sachs Pallavi Malu
5
WSDL overview Web Services Description Language similar in purpose to IDL, but in XML form Operational information about the service Service interface Access protocol Contact endpoint
6
WSDL overview *Where the service is located (service implementation definition) *What the service does (service interface definition) Service Implementation Definition Service Port Binding PortType Message Type Service Interface Definition
7
WSDL elements types: XML schema definitions used to describe the messages exchanged message: abstract definition of data being transmitted. Consists of logical parts, each of which is associated with a definition within some type system portType: set of abstract operations. Each operation refers to an input message and output messages. Support four types of operation: One-way, Request- Response, Solicit-response, Notification. binding: concrete protocol and data format specification for the operations and messages defined by a particular portType port: communication endpoint for a binding service: set of related ports from one service provider
8
WSDL -> CPA element mapping CPAWSDL - operations that the service can offer - operations that the service can invoke
9
WSDL -> CPA element mapping CPAWSDL Assumption: Vanilla SOAP binding (use of attachments will require MIME binding)
10
CPA -> WSDL element mapping One WSDL document per CPA CollarationRole element No element for notification and solicit/response operations Preliminary conclusion: There is sufficient information in the CPA to generate WSDL definitions for all the parties involved
11
Example Rosettanet PIP3A4 (from CPPA 2.0 appendices) Simplifying assumptions Asynchronous communication Acknowledgments/exceptions modeled as one- way/notification operations All operations of type one-way or notification Vanilla SOAP binding only Review example xsds
12
Open issues Project timeline Project deliverables Sub-team recruiting How to exploit WSDL extensibility constructs to achieve tighter integration How to deal with specifications that are not yet submitted to the standards bodies
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.