Join point interfaces for safe and flexible decoupling of aspects

Bodden, Eric; Tanter, Éric; Inostroza, Milton

doi:10.1145/2559933

Cited by 39 publications

(103 citation statements)

References 54 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…An interesting consequence of this granularity is that we are able to express opaque and observable reactions. Both kinds of reactions support stronger encapsulation and guarantees in presence of aspects, and therefore fit in the line of work on modular reasoning about aspects [10,41,51,54].…”

Section: Distributed Aspect Languages and Systemsmentioning

confidence: 56%

See 1 more Smart Citation

Chemical foundations of distributed aspects

Tabareau

Tanter

2018

Distrib. Comput.

Self Cite

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

Section: Distributed Aspect Languages and Systemsmentioning

confidence: 56%

“…This issue has raised considerable debate in the AOP community [32,50], and several proposal have been made to restrict the freedom enjoyed by aspects (e.g. [10,41,42,51,52]). We now present three variants of weaving semantics.…”

Section: Customized Reactionsmentioning

confidence: 99%

Chemical foundations of distributed aspects

Tabareau

Tanter

2018

Distrib. Comput.

Self Cite

View full text Add to dashboard Cite

show abstract

“…According to JPI notation, join point interfaces act as a bridge to let in the UML class instance catches up the result of the defined aspect's method [1] [2] [3]. Communication between aspects and classes instances is synchronous.…”

Section: Jpi Uml Sequence Diagramsmentioning

confidence: 99%

“…First, aspects define pointcut PC rules, which alter advised classes' behavior; base classes are completely oblivious about changes to their behavior and structure during program execution. Second, changes in the signature of advised methods of target classes can produce ineffective or spurious aspects, i.e., occurrences of the fragile pointcut problem [1] [3]. Furthermore, [2] [3] [9] observe that dependencies between classes and aspects compromise independent development of base modules and aspects code.…”

Section: Introductionmentioning

confidence: 99%

JPI UML Software Modeling

Vidal-Silva¹,

López²,

Schmal³

et al. 2015

ijacsa

View full text Add to dashboard Cite

Abstract-Aspect-Oriented Programming AOP extends object-oriented programming OOP with aspects to modularize crosscutting behavior on classes by means of aspects to advise base code in the occurrence of join points according to pointcut rules definition. However, join points introduce dependencies between aspects and base code, a great issue to achieve an effective independent development of software modules. Join Point Interfaces JPI represent join points using interfaces between classes and aspect, thus these modules do not depend of each other. Nevertheless, since like AOP, JPI is a programming methodology; thus, for a complete aspect-oriented software development process, it is necessary to define JPI requirements and JPI modeling phases.Towards previous goal, this article proposes JPI UML class and sequence diagrams for modeling JPI software solutions. A purpose of these diagrams is to facilitate understanding the structure and behavior of JPI programs. As an application example, this article applies the JPI UML diagrams proposal on a case study and analyzes the associated JPI code to prove their hegemony.

show abstract

“…event inheritance. Previous work [14][15][16] enables modular type checking of subjects and observers in the presence of event subtyping.…”

Section: Introductionmentioning

confidence: 99%

Modular Reasoning in the Presence of Event Subtyping

Bagherzadeh

Dyer

Fernando

et al. 2016

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Separating crosscutting concerns while preserving modular reasoning is challenging. Type-based interfaces (event types) separate modularized crosscutting concerns (observers) and traditional object-oriented concerns (subjects). Event types paired with event specifications have been shown to be effective in enabling modular reasoning about subjects and observers. Similar to class subtyping there are benefits to organizing event types into subtyping hierarchies. However, unrelated behaviors of observers and their arbitrary execution orders could cause unique, somewhat counterintuitive, reasoning challenges in the presence of event subtyping. These challenges threaten both tractability of reasoning and reuse of event types. This work makes three contributions. First, we pose and explain these challenges. Second, we propose an event-based calculus to show how these challenges can be overcome. Finally, we present modular reasoning rules of our technique, and show its applicability to other event-based techniques including join point types. AbstractSeparating crosscutting concerns while preserving modular reasoning is challenging. Type-based interfaces (event types) separate modularized crosscutting concerns (observers) and traditional object-oriented concerns (subjects). Event types paired with event specifications were shown to be effective in enabling modular reasoning about subjects and observers. Similar to class subtyping, organizing event types into subtyping hierarchies is beneficial. However, unrelated behaviors of observers and their arbitrary execution orders could cause unique, somewhat counterintuitive, reasoning challenges in the presence of event subtyping. These challenges threaten both tractability of reasoning and reuse of event types. This work makes three contributions. First, we pose and explain these challenges. Second, we propose an event-based calculus to show how these challenges can be overcome. Finally, we present modular reasoning rules of our technique and show its applicability to other event-based techniques.

show abstract

Join point interfaces for safe and flexible decoupling of aspects

Cited by 39 publications

References 54 publications

Chemical foundations of distributed aspects

Chemical foundations of distributed aspects

JPI UML Software Modeling

Modular Reasoning in the Presence of Event Subtyping

Contact Info

Product

Resources

About