Pointcuts as Functional Queries

Eichberg, Michael; Mezini, Mira; Ostermann, Klaus

doi:10.1007/978-3-540-30477-7_25

Cited by 38 publications

(30 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…One of the most frequent examples of AspectJ usage, the figure editor [15], has also been commonly used for exposing the shortcomings of that language [7,8,17]. It consists of a graphical editor, with several types of elements (squares, circles etc.…”

Section: Pointcut Qualitymentioning

confidence: 99%

See 1 more Smart Citation

User-Defined Join Point Selectors — An Extension Mechanism for Pointcut Languages.

Breuel¹,

Reverbel²

2008

JOT

View full text Add to dashboard Cite

One of the main issues in contemporary AOP languages and frameworks is the expressiveness of the pointcut language. This paper proposes an extension mechanism for enriching pointcut languages with constructs that play the role of "new primitive pointcuts" and allow the creation of pointcuts with greater semantic value. Join point selectors are a generalization of the primitive pointcuts of current pointcut languages. Existing languages, however, do not allow users to create new join point selectors. We present a simple architecture for supporting user-defined join-point selectors as an extension mechanism implemented atop an existing AOP framework. We show examples of user-defined selectors that enhance the quality of pointcuts and make aspect development easier. Moreover, we show that our extension mechanism supports framework-specific selectors, which let aspects cross the boundary of a given framework while still respecting the modularity of that framework.

show abstract

Section: Pointcut Qualitymentioning

confidence: 99%

“…In [8], the authors propose the use of the functional language XQuery as a replacement for current pointcut languages. They run XQuery on an XML representation of Java bytecode.…”

Section: Related Workmentioning

confidence: 99%

User-Defined Join Point Selectors — An Extension Mechanism for Pointcut Languages.

Breuel¹,

Reverbel²

2008

JOT

View full text Add to dashboard Cite

show abstract

“…The pointcut language of AspectJ has three limitations: a) it does not provide a general-purpose mechanism to relate different join points, b) it is not extensible, i.e., the user cannot define further pointcut designators, and c) it does not support semantic pointcuts [89,117], i.e., it specifies how the interesting join points are implemented rather than what these join points are [74].…”

Section: A Query-based Pointcut Languagementioning

confidence: 99%

“…Query-based pointcut languages [74] solve these limitations by using query languages such as XQuery [190]. First, such languages allow a more precise specification of the pointcuts because the semantics of query languages are generally clear.…”

Section: A Query-based Pointcut Languagementioning

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

Performance‐driven instrumentation and mapping strategies using the LARA aspect‐oriented programming approach

et al. 2014

View full text Add to dashboard Cite

Summary The development of applications for high‐performance embedded systems is a long and error‐prone process because in addition to the required functionality, developers must consider various and often conflicting nonfunctional requirements such as performance and/or energy efficiency. The complexity of this process is further exacerbated by the multitude of target architectures and mapping tools. This article describes LARA, an aspect‐oriented programming language that allows programmers to convey domain‐specific knowledge and nonfunctional requirements to a toolchain composed of source‐to‐source transformers, compiler optimizers, and mapping/synthesis tools. LARA is sufficiently flexible to target different tools and host languages while also allowing the specification of compilation strategies to enable efficient generation of software code and hardware cores (using hardware description languages) for hybrid target architectures – a unique feature to the best of our knowledge not found in any other aspect‐oriented programming language. A key feature of LARA is its ability to deal with different models of join points, actions, and attributes. In this article, we describe the LARA approach and evaluate its impact on code instrumentation and analysis and on selecting critical code sections to be migrated to hardware accelerators for two embedded applications from industry. Copyright © 2014 John Wiley & Sons, Ltd.

show abstract

Pointcuts as Functional Queries

Cited by 38 publications

References 12 publications

User-Defined Join Point Selectors — An Extension Mechanism for Pointcut Languages.

User-Defined Join Point Selectors — An Extension Mechanism for Pointcut Languages.

Aspect-Oriented Workflow Languages

Performance‐driven instrumentation and mapping strategies using the LARA aspect‐oriented programming approach

Contact Info

Product

Resources

About