Reliable, Secure, and Transacted Web Service Compositions with AO4BPEL

Charfi, Anis; Schmeling, Benjamin; Heizenreder, Andreas; Mezini, Mira

doi:10.1109/ecows.2006.32

Cited by 40 publications

(49 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In the first application [36,41,42], AO4BPEL aspects are used to implement a process container that provides support for security, reliable messaging, and transactions to BPEL processes. In the second application [35], AO4BPEL aspects are used to implement business rules in BPEL processes in a separate and modular way.…”

Section: Resultsmentioning

confidence: 99%

See 1 more Smart Citation

Aspect-Oriented Workflow Languages

Charfi

Mezini

2006

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

Self Cite

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: Resultsmentioning

confidence: 99%

“…The implementation of the middleware can also profit from such crosscutting modularization mechanisms [41,72,73,152,201].…”

Section: The Need For Crosscutting Mechanismsmentioning

confidence: 99%

Aspect-Oriented Workflow Languages

Charfi

Mezini

2006

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

Self Cite

View full text Add to dashboard Cite

show abstract

“…AO4BPEL is an aspect oriented language to extend BPEL business processes with non-functional properties such as reliable messaging, message encryption and transactions (Charfi, Schmeling, Heizenreder, & Mezini, 2006). Aspects can specify non-functional properties that are woven to services and their activities/tasks; however, a variety of pointcuts is limited in AO4BPEL.…”

Section: Related Workmentioning

confidence: 99%

Leveraging Early Aspects in End-to-End Model Driven Development for Non-Functional Properties in Service Oriented Architecture

Oba

Wada

Suzuki³

2011

Journal of Database Management

View full text Add to dashboard Cite

In Service Oriented Architecture (SOA), each application is often designed with a set of reusable services and a business process. In order to retain the reusability of services, it is important to separate non-functional properties of applications (e.g., security and reliability) from their functional properties. This paper investigates an end-to-end model-driven development framework that separates non-functional properties from functional properties and consistently manages them from high-level business processes to low-level implementation configurations. This framework proposes two key components: (1) a programming language, called BALLAD, for a new per-process strategy to specify non-functional properties for business processes and (2) a graphical modeling method, called FM-SNFPs, to define a series of constraints among non-functional properties. BALLAD leverages the notion of aspects in aspect oriented programming/modeling. Each aspect is used to specify a set of non-functional properties that crosscut multiple services in a business process. FM-SNFPs leverages the notion of feature modeling in order to explicitly define constraints among non-functional properties such as dependency and mutual exclusion constraints. BALLAD and FM-SNFPs can free application developers from manually specifying, maintaining and validating non-functional properties and constraints for services one by one, thereby reducing the burdens/costs in development and maintenance of service-oriented applications. This paper describes the design details of BALLAD and FM-SNFPs, and demonstrates how they are used in developing service-oriented applications. Empirical evaluation results show that BALLAD significantly reduces the costs to implement and maintain non-functional properties in service-oriented applications. BALLAD and FM-SNFPs are designed and implemented efficient and scalable.

show abstract

“…3 Suppose a merchant who runs his online music shop purchases a general affiliate marketing software [9] to advertise at third party web sites denoted as affiliates. In a simplified schema of affiliate marketing, a customer visits an affiliate's site which refers him to the merchant's site.…”

Section: Changes As Crosscutting Requirementsmentioning

confidence: 99%

“…These issuse include database schema evolution with aspects [10] or aspect-oriented extensions of business processes and web services with crosscutting concerns of reliability, security, and transactions [3]. Also, an increased changeability of components implemented using aspect-oriented programming [13,14,18] and aspect-oriented programming with the frame technology [15], as well as enhanced reusability and evolvability of design patterns achieved by using generic aspect-oriented languages to implement them [20] have been reported.…”

Section: Related Workmentioning

confidence: 99%

Developing Applications with Aspect-Oriented Change Realization

Vranić

Bebjak

Menkyna

et al. 2011

Software Engineering Techniques

View full text Add to dashboard Cite

Abstract. An approach to aspect-oriented change realization is proposed in this paper. With aspect-oriented programming changes can be treated explicitly and directly at the programming language level. Aspect-oriented change realizations are mainly based on aspect-oriented design patterns or themselves constitute pattern-like forms in connection to which domain independent change types can be identified. However, it is more convenient to plan changes in a domain specific manner. Domain specific change types can be seen as subtypes of generally applicable change types. This relationship can be maintained in a form of a catalog. Further changes can actually affect the existing aspect-oriented change realizations, which can be solved by adapting the existing change implementation or by implementing an aspect-oriented change realization of the existing change without having to modify its source code. Separating out the changes this way can lead to a kind of aspect-oriented refactoring beneficial to the application as such. As demonstrated partially by the approach evaluation, the problem of change interaction may be avoided to the large extent by using appropriate aspect-oriented development tools, but for a large number of changes, dependencies between them have to be tracked, which could be supported by feature modeling.

show abstract

Reliable, Secure, and Transacted Web Service Compositions with AO4BPEL

Cited by 40 publications

References 4 publications

Aspect-Oriented Workflow Languages

Aspect-Oriented Workflow Languages

Leveraging Early Aspects in End-to-End Model Driven Development for Non-Functional Properties in Service Oriented Architecture

Developing Applications with Aspect-Oriented Change Realization

Contact Info

Product

Resources

About