An Advice for Advice Composition in AspectJ

Takeyama, Fuminobu; Chiba, Shigeru

doi:10.1007/978-3-642-14046-4_9

Cited by 5 publications

(5 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Also, the policy is determined for all shared join points, irrespective of whether the join point is a sending or a receiving statement. Finer-grained resolution of conflict can be found in AspectJ extensions, like the AIRIA extension [4] used in our work. It offers a Resolver construct to define precedence policies for advices.…”

Section: Proposed Approachmentioning

confidence: 99%

“…A total execution order must be obtained from the tree of resolvers starting from the root (see [4] for details). Our insertion of instrumentation advices must cope with such arborescent structures.…”

Section: Composing Advices With Advices In Airiamentioning

confidence: 99%

“…(i) prevention: we use an extension of AspectJ [3], namely the AIRIA resolver construct [4], to control the ordering of aspect advices;…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Detection of Interferences in Aspect-Oriented Programs Using Executable Assertions

Lauret

Waeselynck

Fabre

2012

2012 IEEE 23rd International Symposium on Software Reliability Engineering Workshops

View full text Add to dashboard Cite

Aspect-oriented programming (AOP) is a technique that promotes separation of concerns. Unfortunately, it still suffers from well-known composition issues, in particular from undesirable interferences when multiple concerns are applied at the same join point. In this paper we propose an approach to detect interferences side effect using executable assertions. The assertions are inserted in the aspect chain to detect various types of interferences. The implementation is based on the AIRIA resolver construct, recently introduced to better control conflicting aspects in AspectJ. Resolvers add observation points that were lacking in AspectJ. We propose to take advantage of this to implement automated detection of interferences at execution time. We study the feasibility of this approach and demonstrate it on artificial examples.

show abstract

Section: Proposed Approachmentioning

confidence: 99%

Section: Composing Advices With Advices In Airiamentioning

confidence: 99%

See 1 more Smart Citation

Detection of Interferences in Aspect-Oriented Programs Using Executable Assertions

Lauret

Waeselynck

Fabre

2012

2012 IEEE 23rd International Symposium on Software Reliability Engineering Workshops

View full text Add to dashboard Cite

show abstract

“…It allows programmers to describe a safely-composable aspect. Airia provided a new kind of around advise called resolvers for resolving the interference [17]. A uniqueness of our work is that we have designed a language construct specialized for a specific use-case scenario where aspects are used for building a custom library to be used as a black box.…”

Section: Related Workmentioning

confidence: 99%

Method Shells: Avoiding Conflicts on Destructive Class Extensions by Implicit Context Switches

Takeshita

Chiba

2013

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

We propose method shells, which is a module system for avoiding conflicts on customization by language mechanisms such as aspects in AspectJ and open classes in Ruby. These mechanisms allow programmers to customize a library without rewriting original source code but by only describing differences in a separate file. We call these mechanisms destructive class extensions. A problem with destructive class extensions is conflicts on customization. Different customizations may differently modify the same class. To address this problem, we propose a new module system named method shells. With this system, programmers can avoid conflicts since the module system automatically switches a set of customizations that has to be applied together according to the contexts declared by programmers. We present the idea of this module system and then its formal semantics. We also present an extension of Java that supports method shells.

show abstract

“…Our future work includes another type of code clones caused by language constructs such as using of GluonJ and resolvers of Airia [14]. These constructs are used for controlling scope and precedence order of revisers and described in derivatives.…”

mentioning

confidence: 99%

Feature-oriented programming with family polymorphism

Takeyama

Chiba

2012

Proceedings of the 3rd International Workshop on Variability &Amp; Composition - VariComp '12

Self Cite

View full text Add to dashboard Cite

In feature-oriented programming (FOP), code clones are also important issue. Although an approach called a software product line (SPL) enables to implement products efficiently by reusing most of their code, SPLs implemented by FOP contain a lot of code clones. Code clones are often caused by alternative features and we also found clones in derivatives among alternative features. To resolve this problem, we propose a new FOP language named FeatureGluonJ, which supports family polymorphism with revisers. The code clones among alternative features are separated into another feature and can be shared among the alternative features by extending that feature. Furthermore, clones in derivatives can be removed as well.

show abstract

An Advice for Advice Composition in AspectJ

Cited by 5 publications

References 18 publications

Detection of Interferences in Aspect-Oriented Programs Using Executable Assertions

Detection of Interferences in Aspect-Oriented Programs Using Executable Assertions

Method Shells: Avoiding Conflicts on Destructive Class Extensions by Implicit Context Switches

Feature-oriented programming with family polymorphism

Contact Info

Product

Resources

About