Expressive Pointcuts for Increased Modularity

Ostermann, Klaus; Mezini, Mira; Bockisch, Christoph

doi:10.1007/11531142_10

Cited by 117 publications

(121 citation statements)

References 26 publications

Supporting

Mentioning

117

Contrasting

Unclassified

Order By: Relevance

“…A participant driven join point model looks at the process definition from the perspective of partner interactions. A combined use of these join point models may increase the expressiveness of the AO4BPEL pointcut language [65]. However, a thorough investigation of the usefulness of such an increased expressiveness in the context of Web Services is outside the scope of this paper.…”

Section: Join Point Model and Pointcut Languagementioning

confidence: 99%

AO4BPEL: An Aspect-oriented Extension to BPEL

2007

Self Cite

View full text Add to dashboard Cite

Process-oriented composition languages such as BPEL allow Web Services to be composed into more sophisticated services using a workflow process. However, such languages exhibit some limitations with respect to modularity and flexibility. They do not provide means for a well-modularized specification of crosscutting concerns such as logging, persistence, auditing, and security. They also do not support the dynamic adaptation of composition at runtime. In this paper, we advocate an aspect-oriented approach to Web Service composition and present the design and implementation of AO4BPEL, an aspect-oriented extension to BPEL. We illustrate through examples how AO4BPEL makes the composition specification more modular and the composition itself more flexible and adaptable.

show abstract

Section: Join Point Model and Pointcut Languagementioning

confidence: 99%

AO4BPEL: An Aspect-oriented Extension to BPEL

2007

Self Cite

View full text Add to dashboard Cite

show abstract

“…However, this behavioural property cannot be statically verified upon program evolution in all cases. Moreover, although there are 'behavioural' design rules (that can be expressed using advanced pointcut languages [9,14,15]) that do not need to refer to structural properties in the program's source code, such structural properties are still required in many cases.…”

Section: Problem Analysismentioning

confidence: 99%

Managing the Evolution of Aspect-Oriented Software with Model-Based Pointcuts

Kellens

Mens

Brichau

et al. 2006

ECOOP 2006 – Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. In spite of the more advanced modularisation mechanisms, aspect-oriented programs still suffer from evolution problems. Due to the fragile pointcut problem, seemingly safe modifications to the base code of an aspect-oriented program can have an unexpected impact on the semantics of the pointcuts defined in that program. This can lead to broken aspect functionality due to accidental join point misses and unintended join point captures. We tackle this problem by declaring pointcuts in terms of a conceptual model of the base program, rather than defining them directly in terms of how the base program is structured. As such, we achieve an effective decoupling of the pointcuts from the base program's structure. In addition, the conceptual model provides a means to verify where and why potential fragile pointcut conflicts occur, by imposing structural and semantic constraints on the conceptual model, that can be verified when the base program evolves. To validate our approach we implemented a model-based pointcut mechanism, which we used to define some aspects on SmallWiki, a medium-sized application, and subsequently detected and resolved occurrences of the fragile pointcut problem when this application evolved.

show abstract

“…cflow and cflowbelow in AspectJ [31]). Some proposals have even gone further, proposing history-based pointcuts that are not restricted to the call stack [16,17,34,43]. Also, all distributed aspect languages and systems support distributed control flow, although in a synchronous setting [4,39,44,57,59].…”

Section: Dealing With Causalitymentioning

confidence: 99%

Chemical foundations of distributed aspects

Tabareau

Tanter

2018

Distrib. Comput.

View full text Add to dashboard Cite

Distributed applications are challenging to program because they have to deal with a plethora of concerns, including synchronization, locality, replication, security and fault tolerance. Aspect-oriented programming (AOP) is a paradigm that promotes better modularity by providing means to encapsulate crosscutting concerns in entities called aspects. Over the last years, a number of distributed aspect-oriented programming languages and systems have been proposed, illustrating the benefits of AOP in a distributed setting.Chemical calculi are particularly well-suited to formally specify the behavior of concurrent and distributed systems. The join calculus is a functional name-passing calculus, with both distributed and object-oriented extensions. It is used as the basis of concurrency and distribution features in several mainstream languages like C# (Polyphonic C#, now Cω), OCaml (JoCaml), and Scala Joins. Unsurprisingly, practical programming in the join calculus also suffers from modularity issues when dealing with crosscutting concerns.We propose the Aspect Join Calculus, an aspectoriented and distributed variant of the join calculus that addresses crosscutting and provides a formal foundation for distributed AOP. We develop a minimal aspect join calculus that allows aspects to advise chemical reactions. We show how to deal with causal relations in pointcuts and how to support advanced customizable aspect weaving semantics. We also provide the foun-N. Tabareau

show abstract

Expressive Pointcuts for Increased Modularity

Cited by 117 publications

References 26 publications

AO4BPEL: An Aspect-oriented Extension to BPEL

AO4BPEL: An Aspect-oriented Extension to BPEL

Managing the Evolution of Aspect-Oriented Software with Model-Based Pointcuts

Chemical foundations of distributed aspects

Contact Info

Product

Resources

About