Synonyms for aspectj or Related words with aspectj
Examples of "aspectj"
Compared to the
framework, Spring AOP is less powerful, but also less complicated. Spring 1.2 includes support to configure
aspects in the container. Spring 2.0 added more integration with
; for example, the pointcut language is reused and can be mixed with Spring AOP-based aspects. Further, Spring 2.0 added a Spring Aspects library that uses
to offer common Spring features such as declarative transaction management and dependency injection via
compile-time or load-time weaving. SpringSource also uses
AOP in other Spring projects such as Spring Roo and Spring Insight, with Spring Security also offering an
-based aspect library.
also supports limited forms of pointcut-based static checking and aspect reuse (by inheritance). See the
Programming Guide for a more detailed description of the language.
AspectWerkz is a dynamic, lightweight and high-performance AOP/AOSD framework for Java. It has been merged with the
project, which supports AspectWerkz functionality since
All valid Java programs are also valid
lets programmers define special constructs called "aspects". Aspects can contain several entities unavailable to standard classes. These are:
Many programmers discover
as an enabling technology for other projects, most notably Spring AOP. A sister Spring project, Spring Roo, automatically maintains
inter-type declarations as its principal code generation output.
Academic interest in the semantics and implementation of aspect-oriented languages has surrounded
since its release. The leading research implementation of
is the AspectBench Compiler, or "abc"; it supports extensions for changing the syntax and semantics of the language and forms the basis for many AOP experiments that the
team can no longer support, given its broad user base.
implementation. Thus, JaSkel can be deployed on both cluster and Grid like
The Eclipse project supports both command-line and Ant interfaces. A related Eclipse project has steadily improved the Eclipse IDE support for
Development Tools (AJDT)") and other providers of crosscutting structure. IDE support for emacs, NetBeans, and JBuilder foundered when Xerox put them into open source, but support for Oracle's JDeveloper did appear. IDE support has been key to Java programmers using
and understanding crosscutting concerns.
Some of the important Pointcut expressions supported by
. These expressions can be combined using logical operators.
Key to its success has been engineering and language decisions that make the language usable and programs deployable. The original Xerox
implementation used source weaving, which required access to source code. When Xerox contributed the code to Eclipse,
was reimplemented using the Eclipse Java compiler and a bytecode weaver based on BCEL, so developers could write aspects for code in binary (.class) form. At this time the
language was restricted to support a per-class model essential for incremental compilation and load-time weaving. This made IDE integrations as responsive as their Java counterparts, and it let developers deploy aspects without altering the build process. This led to increased adoption, as
became usable for impatient Java programmers and enterprise-level deployments. Since then, the Eclipse team has increased performance and correctness, upgraded the
language to support Java 5 language features like generics and annotations, and integrated annotation-style pure-java aspects from AspectWerkz.
Pointcut expressions can concisely capture a wide range of events of interests, using wildcards. For example, in
syntax, the move pointcut
can be implemented in many ways, including source-weaving or bytecode-weaving, and directly in the virtual machine (VM). In all cases, the
program becomes a valid Java program that runs in a Java VM. Classes affected by aspects are binary-compatible with unaffected classes (to remain compatible with classes compiled with the unaffected originals). Supporting multiple implementations allows the language to grow as technology changes, and being Java-compatible ensures platform availability.
Gregor Kiczales started and led the Xerox PARC team that eventually developed
. He coined the term "crosscutting". Fourth on the team, Chris Maeda coined the term "aspect-oriented programming." Jim Hugunin and Erik Hilsdale (Xerox PARC team members 12 and 13) were the original compiler and weaver engineers, Mik Kersten implemented the IDE integration and started the Eclipse AJDT project with Adrian Colyer (current lead of the
project) and Andrew Clement (current compiler engineer).
While there are many ways that software can automatically generate code, Roo operates by generating
inter-type declarations (otherwise known as mixins or introductions). This achieves separation of concerns, as the code maintained by Roo is in a different compilation unit from the code a user writes. This means Roo can incrementally modify the
inter-type declarations that it needs to and leave all other files intact.
Gregor Kiczales and colleagues at Xerox PARC developed the explicit concept of AOP, and followed this with the
AOP extension to Java. IBM's research team pursued a tool approach over a language design approach and in 2001 proposed Hyper/J and the Concern Manipulation Environment, which have not seen wide usage. The examples in this article use
as it is the most widely known AOP language.
is an aspect-oriented programming (AOP) extension created at PARC for the Java programming language. It is available in Eclipse Foundation open-source projects, both stand-alone and integrated into Eclipse.
has become a widely used de facto standard for AOP by emphasizing simplicity and usability for end users. It uses Java-like syntax, and included IDE integrations for displaying crosscutting structure since its initial public release in 2001.
Jonas Boner and Alex Vasseur engineered the AspectWerkz project, and later contributed to the
project when it merged in the AspectWerkz annotation style and load-time weaving support.
have revealed the potential to incorporate just-in-time compilation into the execution of aspect-oriented code to address performance demands. At run-time, an aspect weaver could translate aspects in a more efficient manner than traditional, static weaving approaches. Using
on a Java Virtual Machine, dynamic weaving of aspects at run-time has been shown to improve code performance by 26%. While some implementations of just-in-time virtual machines implement this capability through a new virtual machine, some implementations can be designed to use features that already exist in current virtual machines. The requirement of a new virtual machine is contrary to one of the original design goals of
To address these business concerns, an aspect weaver enables the use of widely adopted languages like Java with aspect-oriented programming through minor adaptations such as
which work with existing tools. Instead of developing an entirely new language, the aspect weaver interprets the extensions defined by
and builds "woven" Java code which can then be used by any existing Java compiler. This ensures that any existing object oriented code will still be valid aspect-oriented code and that development will feel like a natural extension of the object-oriented language. The AspectC++ programming language extends C++ through the use of an aspect weaver, offering the additional efficiency over
that is necessary for embedded systems while still retaining the benefits of aspect-oriented programming.
A metaobject protocol is one way to implement aspect-oriented programming. Many of the early founders of MOPs, including Gregor Kiczales, have since moved on to be the primary advocates for aspect-oriented programming. Kiczales et al. of PARC were hired to design
for Java, a language which does not possess a native metaobject protocol.
Copyright © 2017