Pi4soa Implementation Issues WS-CDL Candidate Recommendation December 2005 Pi4 Technologies Ltd.

Slides:



Advertisements
Similar presentations
Testing Relational Database
Advertisements

Web Services Choreography and Process Algebra 29th April 2004 Steve Ross-Talbot Chief Scientist, Enigmatec Corporation LtdEnigmatec Corporation Ltd Chair.
Web Services Choreography Description Language Overview 24th November2004 Steve Ross-Talbot Chief Scientist, Enigmatec Corporation Ltd Chair W3C Web Services.
Web Services Architecture An interoperability architecture for the World Wide Service Network.
Proposal for Interface Extension Simplification Sanjiva Weerawarana September 21, 2003.
Web Services Choreography Description Language Overview 6th December 2004 JP Morgan Steve Ross-Talbot Chair W3C Web Services Activity Co-chair W3C Web.
Lectures on File Management
Web Services Choreography Description Language (WS-CDL) Jacek Kopecký June 2004.
FIPA Interaction Protocol. Request Interaction Protocol Summary –Request Interaction Protocol allows one agent to request another to perform some action.
EAP Channel Bindings Charles Clancy Katrin Hoeper IETF 76 Hiroshima, Japan November 08-13, 2009.
1 Transactions and Web Services. 2 Web Environment Web Service activities form a unit of work, but ACID properties are not always appropriate since Web.
CS 290C: Formal Models for Web Software Lecture 4: Implementing and Verifying Statecharts Specifications Using the Spin Model Checker Instructor: Tevfik.
SOAP Quang Vinh Pham Simon De Baets Université Libre de Bruxelles1.
ZEIT2301 Design of Information Systems Behavioural Design: State Machines School of Engineering and Information Technology Dr Kathryn Merrick.
Solutions to Review Questions. 4.1 Define object, class and instance. The UML Glossary gives these definitions: Object: an instance of a class. Class:
OASIS Reference Model for Service Oriented Architecture 1.0
Object-Oriented Analysis and Design
Software Testing and Quality Assurance
IBM WebSphere survey Kristian Bisgaard Lassen. University of AarhusIBM WebSphere survey2 Tools  WebSphere Application Server Portal Studio Business Integration.
Business Process Orchestration
Computer Science CS425/CS6258/23/20011 The Architecting Phase Class diagrams are further refined in this phase of development Object diagrams are created.
Architectural Design Principles. Outline  Architectural level of design The design of the system in terms of components and connectors and their arrangements.
© Copyright Eliyahu Brutman Programming Techniques Course.
Data Abstraction and Object- Oriented Programming CS351 – Programming Paradigms.
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
Using Classes Object-Oriented Programming Using C++ Second Edition 5.
AICT5 – eProject Project Planning for ICT. Process Centre receives Scenario Group Work Scenario on website in October Assessment Window Individual Work.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 4: Detailing a Use Case.
State Diagrams / System Sequence Diagrams (SSDs)
T Network Application Frameworks and XML Web Services and WSDL Sasu Tarkoma Based on slides by Pekka Nikander.
1 © 2005 course technology University Of Palestine Chapter 6 Storyboarding the User’s Experience.
Chapter 5 Class Design. The Deliverables of the Class Design Process Class diagrams are further refined in this phase of development Object diagrams are.
Multi-Part Requests/ Parent & Child Service Items.
1 The CeNTIE project is supported by the Australian Government through the Advanced Networks Program of the Department of Communications, Information Technology.
Ivan Lanese Computer Science Department University of Bologna/INRIA Italy Amending Choreographies Joint work with Fabrizio Montesi and Gianluigi Zavattaro.
1 Modeling interactions and behavior Lecturer Dr. Mai Fadel.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
The GOOD the BAD the UGLY WS-CDL: the GOOD the BAD the UGLY.
95-843: Service Oriented Architecture 1 Master of Information System Management Service Oriented Architecture Lecture 7: BPEL Some notes selected from.
4. The process specification (プロセス仕様) You will learn: (次の内容を学び) The concept of process specification (プロセス 仕様の概念) Notations for process specification (プロセス.
Collaboration Diagrams CSIS3600. What is a Collaboration Diagram Collaboration diagrams illustrate interactions between objects The collaboration diagram.
Chapter 10 Defining Classes. The Internal Structure of Classes and Objects Object – collection of data and operations, in which the data can be accessed.
SIP working group IETF#70 Essential corrections Keith Drage.
16/11/ Web Services Choreography Requirements Presenter: Emilia Cimpian, NUIG-DERI, 07April W3C Working Draft.
Course: COMS-E6125 Professor: Gail E. Kaiser Student: Shanghao Li (sl2967)
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
HNDIT23082 Lecture 09:Software Testing. Validations and Verification Validation and verification ( V & V ) is the name given to the checking and analysis.
Chapter 7 Classes and Methods III: Static Methods and Variables Lecture Slides to Accompany An Introduction to Computer Science Using Java (2nd Edition)
Fusion Design Overview Object Interaction Graph Visibility Graph Class Descriptions Inheritance Graphs Fusion: Design The overall goal of Design is to.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Communication Diagrams Lecture 8. Introduction  Interaction Diagrams are used to model system dynamics  How do objects change state?  How do objects.
Course: Software Engineering – Design I IntroductionSlide Number 1 What is a specification Description of a (computer) system, which:  is precise;  defines.
Ivan Lanese Computer Science Department University of Bologna/INRIA Italy Adaptive Choreographies Joint work with Mila Dalla Preda, Jacopo Mauro and Maurizio.
Statistical process model Workshop in Ukraine October 2015 Karin Blix Quality coordinator
1 Seminar on SOA Seminar on Service Oriented Architecture BPEL Some notes selected from “Business Process Execution Language for Web Services” by Matjaz.
Business Process Execution Language (BPEL) Pınar Tekin.
PRESENTATION ON SECURE SOCKET LAYER (SSL) BY: ARZOO THAKUR M.E. C.S.E (REGULAR) BATCH
Compositional Choreographies By Fabrizio Montesi and Nobuko Yoshida
Training for developers of X-Road interfaces
T Network Application Frameworks and XML Web Services and WSDL Sasu Tarkoma Based on slides by Pekka Nikander.
Choreography Proposal
Deadlock Freedom by Construction
Distribution and components
TIM 58 Chapter 8: Class and Method Design
Chapter 10: Process Implementation with Executable Models
Lecture 09:Software Testing
BPMN - Business Process Modeling Notations
Measurement reporting in TGh
AICT5 – eProject Project Planning for ICT
Presentation transcript:

pi4soa Implementation Issues WS-CDL Candidate Recommendation December 2005 Pi4 Technologies Ltd

hasChoreographyCompleted It is not clear what states constitute 'completed' The test implies 'successfully-completed' and 'unsuccessfully- completed' However, what happens if a sub-choreography completes with no finalizers, it automatically transitions to the 'closed' state – which would currently not be detected by this function Suggestion: change function description to explicitly list states, and include 'closed' state

Perform bind variable types Need a rule to ensure that the types of the 'this' and 'free' variables are the same type Also, the text says that the variable should use the 'getVariable' function, but should also say that the 'partName' should not be specified – i.e. It should not be possible to bind parts.

Choice Current text says only one element, out of two or more, SHOULD be selected What if choice contains all non-blocking conditional elements and none of them evaluate to true? What if you have non-observable conditions around choice elements that are interactions? These non-observable conditions could equally evaluate to false. Semantics of choice need to be clear from a monitoring and execution perspective, therefore would suggest changing SHOULD to MUST.

Exchange type Currently the type field is optional However, if the associated channel type has identity information, then without the message type, it is not possible to determine how the message will be correlated with the channel instance and choreography session Possibly we could add a rule that indicates that the type must be specified if the channel type has identity details, as these details would only be added when intending to execute/monitor choreo, instead of just as a description

Service endpoint projection Currently difficult to link a Qname for the endpoint description with an element in the WS-CDL description This will be required if we wish to estabslish link between the global and endpoint model, for the purpose of validation and reuse pi4soa projects endpoints based on ParticipantType, and therefore names the services after the ParticipantType – This is not a QName and therefore limits the scope of names that can be used for services – Not a good long term solution for reuse of endpoint descriptions – Possibly participant and role types should be changed from NCName to QName?

Channel Passing (1) Business messages can be correlated to a channel instance and choreography session using identity information derived (through the use of token locators) from the message contents However, channels passed over other channel instances do not carry any business information, and therefore how can they be correlated? Approach taken in pi4soa is currently restricted to use of WS- Addressing endpoint reference, which it stores the identity token values of the channel on which the exchange is occurring – however this is not interoperable, as it relies on prior knowledge of the identity token encoding within the endpoint reference

Channel Passing (2) Channel passing is also restrictive, as it can only be passed within its own exchange This is currently necessary to enable the formal verification to identify where the channels are being passed However, for subsequent versions of CDL, we should investigate the ability to describe message exchanges where a channel's details are passed as part of a business message, but still remain explicit enough for formal verification.

Multipart variable with single part Currently, if a multipart message type has only a single part, it still needs to be accessed using the part name – this is not portable between a WSDL1.1 and WSDL2.0 version of the same interface Suggestion: change the spec to indicate that if multipart message has only single part, then part name is optional

Activity names Not all activity types have a 'name' attribute This causes a problem when associating implementation hooks to the activity Important example is silentAction

hasExchangeOccurred Example: request for quote, while waiting for suitable quote (on refresh loop), until quote accepted – Interaction: --> request for quote Interaction: quote accepted Currently only possible with parallel construct setting state variable to indicate when quote is acceptable, as quote provider as no means to detect when quote has been accepted, and therefore break out of the loop Suggestion: having a 'hasExchangeOccurred' to finish the loop once the quote accept has been received

hasExchangeOccurred (2) Send rfqReceive rfq Receive quoteSend quote Parallel{Parallel{ when quoteAccwhen..... Send quoteAccReceive quoteAcc [rec quoteAcced][rec quoteAcced] when refresh &&when refresh && !quoteAcced..!quoteAcced }}