An Overview of AspectJ
By Gregor Kiczales, Erik Hilsdale, Jim Hugunin, Mik Kersten, Jeffrey Palm, W. Griswold. European Conference on Object-Oriented Programming, 2001
3,500 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Information Systems
View Paper: https://www.semanticscholar.org/paper/282f88f3e89813bba06aa0b23987955b987e9af3
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Christian Kästner
- Sven Apel
- Gunter Saake
- Gregor Kiczales
- Thomas Thüm
- Ina Schaefer
- Thomas Leich
- Jens Meinicke
In Information Systems
- Christian Kästner
- Sven Apel
- Gunter Saake
- Gregor Kiczales
- Mira Mezini
- Thomas Thüm
- Gail C. Murphy
- Mik Kersten
Citations in the corpus
- The FRACTAL component model and its support in Java (2006, methodology): “Aspect/J, for example, could effectively be used to solve the above problem: aspect classes could indeed be used instead of sub-classes, which would solve the combinatory problems (an aspect can be applied to multiple classes and aspects).”
- Delta-Oriented Programming of Software Product Lines (2010, methodology): “The ordering of delta modules within the after clause resembles the precedence order on advice used in aspect-oriented programming, e.g., in A SPECT J [21].”
- Catch me if you can: performance bug detection in the wild (2011, background): “Similarly, aspect-oriented programming implementations such as AspectJ [16] provide dynamic weaving approaches.”
- FeatureIDE: An extensible framework for feature-oriented software development (2014, methodology): “This functionality is developed for DeltaJ and AspectJ in external plug-ins.”
- Dynamic Instrumentation of Production Systems (2004, neutral): “More generally, the notion of augmenting execution with code has been explored in aspect-oriented programming systems like AspectJ[6].”
- A survey on engineering approaches for self-adaptive systems (2015, background): “In Aspect-Oriented Programming (AOP) the program is divided in distinct parts, called concerns.”
- Model-driven Development of Complex Software: A Research Roadmap (2007, background): “Work on separating crosscutting functionality at the programming level has led to the development of aspect-oriented programming (AOP) languages such as Aspect-J [35].”
- An Open Component Model and Its Support in Java (2004, methodology): “Another solution could have been to use an Aspect Oriented Programming (AOP) tool or language, such as AspectJ [ 11 ].”
- Adding trace matching with free variables to AspectJ (2005, background): “The most popular implementation of these ideas is AspectJ [18], an extension of Java.”
- Aspect-oriented programming and modular reasoning (2005, background): “The AspectJ language design contemplates that weaving can happen at any time, even as late as in the interpreter, and implementations have been developed that weave at a range of times [3, 19, 21].”
- Edit automata: enforcement mechanisms for run-time security policies (2005, neutral): “In most cases, these languages can be considered domain-specific aspect-oriented programming languages [9], which have been designed to facilitate the enforcement of security properties.”
- Advice weaving in AspectJ (2004, background): “Advice Weaving in Aspectd Erik Hilsdale PARC 3333 Coyote Hill Rd Palo Alto, CA 94085 +1 650 812 4735 hilsdale @ parc.com Jim Hugunin Want of a Nail Software Sunnyvale, CA +1 650 812 4735 jim-aj@ hugunin.net ABSTRACT This paper describes the implementation of advice weaving in AspectJ.”
- Mylar: a degree-of-interest model for IDEs (2005, background): “When the system is small, the elements related to the task-at-hand are easy to find in such views.”
- Finding application errors and security flaws using PQL: a program query language (2005, neutral): “Maya [7] and AspectJ [25] attach actions based on syntactic properties of individual statements in the sou rce code.”
- Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools (2004, background): “The operational requirement is called an aspect, and the process of weaving it into the functional modules is called aspect weaving [21].”