Region pointcut for AspectJ

Akai, Shumpei; Chiba, Shigeru; Nishizawa, Muga

doi:10.1145/1509276.1509287

Cited by 12 publications

(9 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In other words, the method is a "nop". The first and third parameter relate to @Java's internal representation: they are machine-generate unique string identifiers for the expression 1 . @AspectJ uses this string to pattern match the correct expression.…”

Section: Expressionsmentioning

confidence: 99%

“…However, the implementation is rigid in that only the so-called loop arguments (the iterating variable, the loop condition, and the increment) can be accessed, and it also suffers from some severe limitations, like supporting only ascending loops. Akai et al [1] describe the concept of region pointcut as an extension to AspectJ. A region pointcut may select a particular code section in order to deal with synchronization and transaction management.…”

Section: @Aspectj At Workmentioning

confidence: 99%

“…[1,15,19,21]); in fact, there may be Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee.…”

Section: Introductionmentioning

confidence: 99%

“…Several solutions have been proposed. For instance, many work propose to enhance the pointcut language with richer constructs, that are able to capture join points at a finer level (e.g., [1,13,16,19]). Other works prefer to extend the syntax of the target language (usually Java) to explicitly mark portions of code as advisable (for instance [3,12]), and then provide a lightweight extension to the pointcut language to select them.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Fine-grained annotations for pointcuts with a finer granularity

Cazzola

Vacchi

2013

Proceedings of the 28th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

A number of authors have suggested that AspectJ-like pointcut languages are too limited, and that they cannot select every possible join point in a program. Many enhanced pointcut languages have been proposed; they require virtually no change to the original code, but their improved expressive power comes often at the cost of making the pointcut expression too tightly connected with the structure of the programs that are being advised. Other solutions consist in simple extensions to the base language; they require only small changes to the original code, but they frequently serve no other immediate purpose than exposing pieces of code to the weaver. Annotations are a form of metadata that has been introduced in Java 5. Annotations have a number of uses: they may provide hints to the compiler, information to code processing tools and they can be retained at runtime. At the moment of writing, runtime-accessible annotations in the Java programming language can only be applied to classes, fields and methods. The support to annotate expressions and blocks feels like a natural extension to Java's annotation model, that can be also exploited to expose join points at a finer-grained level. In this paper we present an extension to the AspectJ language to select block and expression annotations in the @Java language extension.

show abstract

Section: Expressionsmentioning

confidence: 99%

Section: @Aspectj At Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Fine-grained annotations for pointcuts with a finer granularity

Cazzola

Vacchi

2013

Proceedings of the 28th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

show abstract

“…Cunha et al [4] presented a collection of well-known, high-level concurrency patterns and mechanisms, such as synchronization and barrier. In [5,22,23], a loop joint model, a region aspect, and a synchronized block join point were proposed for parallelization in AspectJ. Rashid et al [8] proposed a persistence model of Java objects using an AOP approach.…”

Section: Related Workmentioning

confidence: 99%

Aspect-oriented development of cluster computing software

2011

View full text Add to dashboard Cite

In complex software systems, modularity and readability tend to be degraded owing to inseparable interactions between concerns that are distinct features in a program. Such interactions result in tangled code that is hard to develop and maintain. Aspect-Oriented Programming (AOP) is a powerful method for modularizing source code and for decoupling cross-cutting concerns. A decade of growing research on AOP has brought the paradigm into many exciting areas. However, pioneering work on AOP has not flourished enough to enrich the design of distributed systems using the refined AOP paradigm. This article investigates three case studies that cover time-honored issues such as fault-tolerant computing, network heterogeneity, and object replication in the cluster computing community using the AOP paradigm. The aspects that we define here are simple, intuitive, and reusable. Our intensive experiences show that (i) AOP can improve the modularity of cluster computing software by separating the source code into base and instrumented parts, and (ii) AOP helps developers to deploy additional features to legacy cluster computing soft-A preliminary version [1] of this paper was presented at IEEE Cluster 2007,

show abstract

On the modularization and reuse of exception handling with aspects

et al. 2009

View full text Add to dashboard Cite

This paper presents an in‐depth study of the adequacy of the AspectJ language for modularizing and reusing exception‐handling code. The study consisted of refactoring existing applications so that the code responsible for implementing error‐handling strategies was moved to newly created exception handler aspects. We have performed quantitative assessments of five systems—four object‐oriented and one aspect‐oriented—based on four key quality attributes, namely separation of concerns, coupling, cohesion, and conciseness. Our investigation also included a multi‐perspective analysis of the refactored systems, including (i) the extent to which error‐handling aspects can be reused, (ii) the beneficial and harmful aspectization scenarios for exception handling, and (iii) the scalability of AOP to support the modularization of exception handling in the presence of other aspects. Copyright © 2009 John Wiley & Sons, Ltd.

show abstract

Region pointcut for AspectJ

Cited by 12 publications

References 8 publications

Fine-grained annotations for pointcuts with a finer granularity

Fine-grained annotations for pointcuts with a finer granularity

Aspect-oriented development of cluster computing software

On the modularization and reuse of exception handling with aspects

Contact Info

Product

Resources

About