Dynamic and selective combination of extensions in component-based applications

Truyen, Eddy; Vanhaute, Bart; Joosen, Wouter; Verbaeten, Pierre; Jôrgensen, Bo Nørregaard

doi:10.1109/icse.2001.919097

Cited by 49 publications

(46 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Another related approach is the Lasagne project [48] that provides dynamic weaving/unweaving of aspects that is similar to the JAC implementation. The dynamicity is achieved by policy selection on the client.…”

Section: Dynamic Aopmentioning

confidence: 99%

JAC: an aspect‐based distributed dynamic framework

et al. 2004

View full text Add to dashboard Cite

SUMMARYIn this paper, we present the JAC (Java Aspect Components) framework for building aspect-oriented distributed applications in Java. This paper describes the aspect-oriented programming model and the architectural details of the framework implementation. The framework enables extension of application semantics for handling well-separated concerns. This is achieved with a software entity called an aspect component (AC). ACs provide distributed pointcuts, dynamic wrappers and metamodel annotations. Distributed pointcuts are a key feature of our framework. They enable the definition of crosscutting structures that do not need to be located on a single host. ACs are dynamic. They can be added, removed, and controlled at runtime. This enables our framework for use in highly dynamic environments where adaptable software is needed.

show abstract

Section: Dynamic Aopmentioning

confidence: 99%

JAC: an aspect‐based distributed dynamic framework

et al. 2004

View full text Add to dashboard Cite

show abstract

“…Indeed, there is a large body of previous work in which aspects are applied in the middleware domain: JAC [26], Lasagna [27], PROSE [28], JAsCo [29], and others.…”

Section: Comparison With Jboss and Springmentioning

confidence: 99%

“…Different JVMs use different schemes for storing a stack snapshot in instances of the java.lang.Throwable class 27 (this information is used, for example, by the method java.lang.Exception.printStackTrace()). Such a stack snapshot (obtained via an instance of Throwable, or any other JVM-specific means) can be examined in order to test for cflow/cflowbelow conditions at runtime.…”

Section: Super()mentioning

confidence: 99%

Shakeins: Nonintrusive Aspects for Middleware Frameworks

Cohen

Gil

2006

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Shakeins are a novel programming construct which, like mixins and generic classes, generates new classes from existing ones in a universal, uniform, and automatic manner: From a given class, a shakein generates a new class which has the same type as the original, but with different data and code implementation. We argue that shakeins are restricted, yet less chaotic, aspects. We further claim that shakeins are well suited for the introduction of aspect-oriented programming (AOP) into existing middleware applications. We introduce the ASPECTJ2EE language which, with the help of shakeins and a new deploy-time weaving mechanism, brings the blessings of AOP to the J2EE framework. A unique advantage of ASPECTJ2EE, which is less general (and hence less complicated) than AS-PECTJ, is that it can be smoothly integrated into J2EE implementations without breaking their architecture.

show abstract

“…Interfaces to this meta-level are defined by meta-object protocols (MOP) like interceptors as they are used in the context of this paper. Several recent publications [23,24] leverage interceptors for building frameworks that more or less try to partly hide the complexity of metaprogramming or to add a higher abstraction level. As we are using interceptors only as the means for integrating orthogonal functionality, current research on this field is slightly out of this paper's scope.…”

Section: Meta-programmingmentioning

confidence: 99%

Client-Side Component Caching

Pohl

Schill

2003

Distributed Applications and Interoperable Systems

View full text Add to dashboard Cite

Abstract. Locality of referenced data is an important aspect for distributed computing. Caching is commonly employed to achieve this goal. However, when using current component-oriented middleware client application programmers have to take care of this non-functional aspect by themselves, without direct support from middleware facilities or design tools. The paper at hand describes a novel approach to disburden them from this non-trivial, error-prone task by transparently integrating caching as an orthogonal middleware service using interceptors which are preconfigured at design-time using standard UML extension mechanisms. An advanced mechanism for dynamic adaptation of the caching service to changing access characteristics is introduced in the second part.

show abstract

Dynamic and selective combination of extensions in component-based applications

Cited by 49 publications

References 8 publications

JAC: an aspect‐based distributed dynamic framework

JAC: an aspect‐based distributed dynamic framework

Shakeins: Nonintrusive Aspects for Middleware Frameworks

Client-Side Component Caching

Contact Info

Product

Resources

About