Discussing aspects of AOP

Elrad, Tzilla; Akşit, Mehmet; Kiczales, Gregor; Lieberherr, Karl; Ossher, Harold

doi:10.1145/383845.383854

Cited by 135 publications

(96 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Aspect-oriented programming (AOP) is the name given to a set of techniques based on the idea that software is better programmed by separately specifying the various concerns (or aspects), properties, or areas of interest of a system, and describing their relationships [2]. Ultimately, the programmer relies on the underlying AOP environment to weave (or compose) the concerns together into a coherent program.…”

Section: Aspect-oriented Programmingmentioning

confidence: 99%

“…Again, one could adopt this programming discipline in any language, but AOP languages help support this kind of separation through mechanisms like join points, weaving, etc. [2]. Typically, one might talk about functional and non-functional aspects.…”

Section: Introductionmentioning

confidence: 99%

“…In our experiment, we use AspectJ [2] as a representative of aspect-oriented programming languages and transactions [3] as a fundamental paradigm to handle concurrency and failures. We proceed in an incremental manner, where we try to achieve three goals: from the most ambitious to the less ambitious one.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

AOP: Does It Make Sense? The Case of Concurrency and Failures

Kienzle

Guerraoui

2002

ECOOP 2002 — Object-Oriented Programming

View full text Add to dashboard Cite

Abstract. Concurrency and failures are fundamental problems in distributed computing. One likes to think that the mechanisms needed to address these problems can be separated from the rest of the distributed application: in modern words, these mechanisms could be aspectized. Does this however make sense?This paper relates an experience that conveys our initial and indeed biased intuition that the answer is in general no. Except for simple academic examples, it is hard and even potentially dangerous to separate concurrency control and failure management from the actual application.We point out the very facts that (1) an aspect-oriented language can, pretty much like a macro language, be beneficial for code factorization (but should be reserved to experienced programmers), and (2) concurrency and failures are particularly hard to aspectize because they are usually part of the phenomenon that objects should simulate. They are in this sense different than other concerns, like for instance tracing, which might be easier to aspectize.

show abstract

Section: Aspect-oriented Programmingmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

AOP: Does It Make Sense? The Case of Concurrency and Failures

Kienzle

Guerraoui

2002

ECOOP 2002 — Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

“…See [14] for details. 8 In this model [12], every class loader has a parent class loader. Whenever a class loader is asked to load a class, it first delegates the request to its parent.…”

Section: Class Loading Issuesmentioning

confidence: 99%

“…Containers are service components that enhance application component classes with predefined and packaged sets of aspect requirements. They provide serverside join points for aspects [16,8] that crosscut the central concerns of multiple EJB components. Dynamic proxies, used as client stubs, provide similar join points at the client side.…”

Section: Introductionmentioning

confidence: 99%

The JBoss Extensible Server

Fleury¹,

Reverbel

2003

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. JBoss is an extensible, reflective, and dynamically reconfigurable Java application server. It includes a set of components that implement the J2EE specification, but its scope goes well beyond J2EE. JBoss is open-ended middleware, in the sense that users can extend middleware services by dynamically deploying new components into a running server. We believe that no other application server currently offers such a degree of extensibility. This paper focuses on two major architectural parts of JBoss: its middleware component model, based on the JMX model, and its meta-level architecture for generalized EJBs. The former requires a novel class loading model, which JBoss implements. The latter includes a powerful and flexible remote method invocation model, based on dynamic proxies, and relies on systematic usage of interceptors as aspect-oriented programming artifacts.

show abstract

Implementing design patterns in Object Teams

Monteiro

Gomes

2012

Softw Pract Exp

View full text Add to dashboard Cite

SUMMARY This paper presents a study of the support for modularity of Object Teams, an aspect‐oriented language backwards compatible with Java. The study is based on implementations in Object Teams of two complete collections of the Gang‐of‐Four design patterns. An analysis of the implementations is provided, in terms of advantages of Object Teams over Java with respect to modularity, module composition and reuse. We present a systematic comparison with a functionally equivalent collection of implementations in AspectJ, regarding five modularity properties: locality, reusability, composition transparency, (un)pluggability and extensibility. Object Teams yields broadly comparable results in terms of the first four properties. Object Teams yields better results as regards flexible module extensibility, composition at the instance level and enclosing multiple pattern participants into a larger, cohesive module. AspectJ is more successful than Object Teams in the Singleton pattern because of its ability to intercept constructor events. Copyright © 2012 John Wiley & Sons, Ltd.

show abstract

Discussing aspects of AOP

Cited by 135 publications

References 0 publications

AOP: Does It Make Sense? The Case of Concurrency and Failures

AOP: Does It Make Sense? The Case of Concurrency and Failures

The JBoss Extensible Server

Implementing design patterns in Object Teams

Contact Info

Product

Resources

About