Isolating Process-Level Concerns Using Padus

Braem, Mathieu; Verlaenen, Kris; Joncheere, Niels; Vanderperren, Wim; Straeten, Ragnhild Van Der; Truyen, Eddy; Joosen, Wouter; Jonckers, Viviane

doi:10.1007/11841760_9

Cited by 45 publications

(50 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In addition, the activity packageSequence contains two invoke activities for calling Berlin Air Web Service (lines [26][27][28] and MyHotels Web Service (lines 29-31). Moreover, another assign activity is used to copy the flight and hotel data from the variables flightresponse and hotelresponse into the variable clien- <reply name="replyToClient" partnerLink="client" portType="travelServicePT" The specifications of the flight process and the hotel process in BPEL are similar to the travel package process, whereby the flight process invokes the Web Services of Tunis Air and Berlin Air, and the hotel process invokes the Web Services of MyHotels and MagicHotels.…”

Section: The Travel Agency Scenario In Bpelmentioning

confidence: 99%

“…Both operations startTimer and stopTimer take a parameter, which identifies the monitored activity. The input data of the invoke activities that call these operations is set using appropriate assign activities (lines 12-17 and lines [23][24][25][26][27][28].…”

Section: Measurement Of Activity Execution Timementioning

confidence: 99%

“…For example, the advice language of AspectJ is Java. In aspect-oriented workflow languages, the advice language should be the same as the base workflow language [26,34] to avoid any paradigm mismatches for the workflow designers. There are some proposals for using some programming language as advice language [57] in a similar way to BPELJ [18], which allows adding Java code snippets to BPEL processes.…”

Section: Advicementioning

confidence: 99%

“…It takes a workflow process and a set of workflow aspects as input and generates a new workflow process as output. This approach is implemented in the composition mechanism of the recent aspectoriented workflow language Padus [26].…”

Section: Process Transformationmentioning

confidence: 99%

See 3 more Smart Citations

Aspect-Oriented Workflow Languages

Charfi

Mezini

2006

On the Move to Meaningful Internet Systems 2006: CoopIS, DOA, GADA, and ODBASE

View full text Add to dashboard Cite

Erklärung: Hiermit erkläre ich, daß ich die vorliegende Arbeit selbstständig und unter ausschließlicher Verwendung der angegebenen Quellen und Hilfsmittel angefertigt habe. Darmstadt, den 12. Dezember 2006To my parents,To my wife, To my brother and my sister AcknowledgmentsFirstly, I would like to thank sincerely my advisor Prof. Dr. Mira Mezini for giving me the chance to work in her team, for her support and guidance during the three years of my PhD work, and for providing valuable feedback on early drafts of this thesis. I am also grateful to Prof. Dr. Gustavo Alonso for being the second advisor of this dissertation.Moreover, I thank the German Science Foundation (DFG) for supporting this work in the framework of the research school on Electronic Commerce at Darmstadt University of Technology. I also thank the Tunisian Ministry of Higher Education for having supported my previous studies in Computer Science at Munich University of Technology.In addition, I am indebted to all my colleagues at the Software Technology Group and at the Aspect-Oriented Programming Group for the excellent and productive working environment. I thank Gudrun Jörs for her continuous support.I am also grateful to Tom Dinkelaker, Slim Kallel, Vaidas Gasiunas, Sven Kloppenburg, and Michael Eichberg for proof-reading parts of this thesis and/or for giving feedback on the dissertation talk. Thanks also to Prof. Dr. Klaus Ostermann, who allowed me to reuse the Latex template of his dissertation.My students Andreas Heizenreder, Benjamin Schmeling, and Leo Shang contributed to the work described in this thesis by implementing some parts of the process container framework and the AO4BPEL engine in the context of their diploma thesis.Last but certainly not least, I thank deeply my family for their infinite support. I am indebted to my dear parents who encouraged me to study abroad and to pursue my doctoral studies. I owe much of this success to my wife for her support during the difficult time of writing this thesis. I thank my sister and my brother for their love. AbstractThis thesis focuses on the modularity of workflow process specifications. In particular, it studies the expression support for crosscutting concerns and workflow changes in current workflow languages and workflow management systems. To illustrate the issues, two workflow languages are considered: a visual graphbased language and the Web Service composition language BPEL.This thesis starts by describing the implementation of several crosscutting concerns such as data collection for billing, activity execution time measurement, and security in typical processes of a travel agency. When examining the resulting workflow specifications, the following observations are made.First, the workflow constructs that implement a crosscutting concern cannot be encapsulated in a separate module with a well-defined interface. They are rather scattered across the specifications of several workflow processes. Second, the workflow specifications that result after adding the implementation of a cro...

show abstract

Section: The Travel Agency Scenario In Bpelmentioning

confidence: 99%

Section: Measurement Of Activity Execution Timementioning

confidence: 99%

Section: Advicementioning

confidence: 99%

Section: Process Transformationmentioning

confidence: 99%

See 2 more Smart Citations

Aspect-Oriented Workflow Languages

Charfi

Mezini

2006

On the Move to Meaningful Internet Systems 2006: CoopIS, DOA, GADA, and ODBASE

View full text Add to dashboard Cite

show abstract

“…Some more recent AOP approaches are explicitly targeted at Web services. With Padus [7] and Ao4BPEL [9], aspects can be (un)plugged into BPEL composition processes. Since BPEL processes consist of a set of activities, joinpoints in Padus and AO4BPEL are well-defined points in the execution of the processes: each BPEL activity is a possible joinpoint.…”

Section: Error Handling Revisitedmentioning

confidence: 99%

Modularization of Distributed Web Services Using Aspects with Explicit Distribution (AWED)

Navarro

Südholt

Vanderperren

et al. 2006

On the Move to Meaningful Internet Systems 2006: CoopIS, DOA, GADA, and ODBASE

Self Cite

View full text Add to dashboard Cite

Abstract. With the adoption of Web services technology to realize Service Oriented Architectures, the need arises for more flexible and dynamic technologies for the just-in-time integration and composition of services. As the runtime integration, selection and management of services involves a variety of crosscutting concerns, such as error handling, service monitoring, and QoS enforcements, Aspect Oriented Programming (AOP) is useful to modularize such concerns.In this paper we investigate aspect-oriented support for crosscutting concerns of distributed management of web service compositions. We propose to use a distributed AOP approach, Aspects with Explicit Distribution (AWED), to modularize such concerns in a distributed variant of the Web Services Management Layer (WSML). Concretely, we present three contributions. First, we present an extension of the WSML to distributed compositions. Second, we present two extensions to AWED's aspect language which are useful for the modularization of crosscutting concerns of web services: support for chains of (a)synchronous remote advice that communicate through futures, and support for different modes of parameter passing between remote pointcuts and advice. Third, we illustrate our approach by investigating error handling in distributed web compositions.

show abstract

An Aspect Oriented Approach for Context-Aware Service Domain Adapted to E-Business

Boukadi¹,

Ghédira²,

Vincent³

2008

Advanced Information Systems Engineering

View full text Add to dashboard Cite

This paper proposes an architecture for a high-level structure called Service Domain which orchestrates a set a of related IT services based on BPEL specification. Service Domain was developed to enhance the Web service concept to suit e-business collaboration. Service Domains are developed to be context aware. Our approach highlights the benefits of bringing Aspect Oriented Programming to ensure context aware services. Thus, context awareness is guaranteed by enhancing BPEL execution using Aspect oriented paradigms. The proposed approach is illustrated with a running example that shows how Service Domain presents different behaviours according to the context changes.

show abstract

Isolating Process-Level Concerns Using Padus

Cited by 45 publications

References 18 publications

Aspect-Oriented Workflow Languages

Aspect-Oriented Workflow Languages

Modularization of Distributed Web Services Using Aspects with Explicit Distribution (AWED)

An Aspect Oriented Approach for Context-Aware Service Domain Adapted to E-Business

Contact Info

Product

Resources

About