Stateful Aspects in JAsCo

Vanderperren, Wim; Suvee, Davy; Cibran, Maria; Fraine, Bruno De

doi:10.1007/11550679_13

Cited by 55 publications

(34 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The Alpha aspect language also uses a logic programming language for the specification of pointcuts and enhances the expressiveness by providing diverse automatically-derived models of the program and associated predicates that can, for example, reason over the entire state and execution history [15]. EAOP [14] and JAsCo [20] offer event-based or stateful pointcuts that allow to express the activation of an aspect based on a sequence of events during the program's execution.…”

Section: Discussionmentioning

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

Section: Discussionmentioning

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

show abstract

“…The use of logic rules for writing model documentation was not considered. EAOP [22] and JAsCo [23] offer event-based or stateful pointcuts that allow to express the activation of an aspect based on a sequence of events during the program's execution.…”

Section: Expressive Pointcut Languagesmentioning

confidence: 99%

Application-Specific Models and Pointcuts Using a Logic Meta Language

Brichau

Kellens

Gybels

et al. 2007

Advances in Smalltalk

View full text Add to dashboard Cite

In contemporary aspect-oriented languages, pointcuts are usually specified directly in terms of the structure of the source code. The definition of such low-level pointcuts requires aspect developers to have a profound understanding of the entire application's implementation and often leads to complex, fragile, and hard to maintain pointcut definitions. To resolve these issues, we present an aspect-oriented programming system that features a logic-based pointcut language that is open such that it can be extended with application-specific pointcut predicates. These predicates define an application-specific model that serves as a contract that base-program developers provide and aspect developers can depend upon. As a result, pointcuts can be specified in terms of this more high-level model of the application which confines all intricate implementation details that are otherwise exposed in the pointcut definitions themselves.

show abstract

“…Vanderperren et al [19] propose the stateful pointcut language JAsCo also based on the above model. Pointcuts trigger transitions in a deterministic finite automaton and advice can be attached to each pointcut.…”

Section: Other Approachesmentioning

confidence: 99%

Tracechecks: Defining Semantic Interfaces with Temporal Logic

Bodden

Stolz

2006

Software Composition

View full text Add to dashboard Cite

Abstract. Tracechecks are a formalism based on linear temporal logic (LTL) with variable bindings and pointcuts of the aspect-oriented language AspectJ for the purpose of verification. We demonstrate how tracechecks can be used to model temporal assertions. These assertions reason about the dynamic control flow of an application. They can be used to formally define the semantic interface of classes. We explain in detail how we make use of AspectJ pointcuts to derive a formal model of an existing application and use LTL to express temporal assertions over this model.We developed a reference implementation with the abc compiler showing that the tool can be applied in practice and is memory-efficient.In addition we show how tracechecks can be deployed as Java5 annotations, yielding a system which is fully compliant with any Java compiler and hiding any peculiarities of aspect-oriented programming from the user. Through annotations, the tracecheck specifications become a semantic part of an interface. Consumers of such a component can then take advantage of the contained annotations by applying our tool and have their use of this component automatically checked at runtime for compliance with the intent of the component provider.

show abstract

Stateful Aspects in JAsCo

Cited by 55 publications

References 10 publications

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

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

Application-Specific Models and Pointcuts Using a Logic Meta Language

Tracechecks: Defining Semantic Interfaces with Temporal Logic

Contact Info

Product

Resources

About