Using AOP to Customize a Reflective Middleware

Cacho, Nélio; Batista, Thaís

doi:10.1007/11575801_13

Cited by 2 publications

(3 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, most of the existing works in the literature applies reflection to support AOP (e.g. [32]). In this work we apply AOP to modularize reflective features of a middleware platform in order to modularize them and to leverage the adaptability support provided by reflective middleware.…”

Section: Related Workmentioning

confidence: 99%

Improving modularity of reflective middleware with aspect-oriented programming

Cacho

Batista

Garcia

et al. 2006

Proceedings of the 6th International Workshop on Software Engineering and Middleware

View full text Add to dashboard Cite

Reflective middleware has been proposed as an effective way to enhance adaptability of component-oriented middleware architectures. To be effectively adaptable, the implementation of reflective middleware needs to be modular. However, some recently emerged applications such as mobile, pervasive, and embedded applications have imposed more stringent modularity requirements to the middleware design. They require support for the conception of a minimal middleware while promoting finegrained modularity of reflective middleware features. The key problem is that fundamental mechanisms for decomposing reflective middleware implementations, such as object-oriented ones, suffer from not providing the proper means to achieve the required level of localizing reflection-specific concerns. This paper presents a systematic investigation on how aspect-oriented programming scales up to improve modularity of typical reflection-specific crosscutting concerns. We have quantitatively compared Java and AspectJ implementations of an OpenORBcompliant reflective middleware using separation of concerns metrics.

show abstract

Section: Related Workmentioning

confidence: 99%

Improving modularity of reflective middleware with aspect-oriented programming

Cacho

Batista

Garcia

et al. 2006

Proceedings of the 6th International Workshop on Software Engineering and Middleware

View full text Add to dashboard Cite

show abstract

“…[13] modularises the crosscutting concerns of a CORBA ORB. Similarly, [2] identifies that in reflective middleware, reflection crosscuts core middleware functionality; hence, aspects are used to customise the reflective MOPs. Finally, Demir et al [14] present an aspect-oriented IDL that allow developers to insert application-level behaviour lower in the middleware stack, bypassing unnecessary layer processing, e.g.…”

Section: Customising Middlewarementioning

confidence: 99%

“…Although the two are highly complimentary [1], they have typically been utilised in isolation for adaptive systems, or combined at different stages of the development lifecycle e.g. using aspects to customise reflective middleware at design time [2], using aspect weaving at compile time to make systems adapt-ready [3] [4], or layering dynamic aspects atop reflection meta-object protocols (MOP) [5] [6]. This demonstrates that the two approaches benefit one another; we wish to explore these benefits further by combining reflection and aspects at runtime.…”

Section: Introductionmentioning

confidence: 99%

The case for aspect-oriented reflective middleware

Grace

Truyen

Lagaisse

et al. 2007

Proceedings of the 6th International Workshop on Adaptive and Reflective Middleware: Held at the ACM/IFIP/USENIX International

View full text Add to dashboard Cite

The emergence of applications domains such as pervasive and autonomic computing has increased the need for customisation and dynamic adaptation of both distributed systems, and the underlying middleware platforms. Two highly complementary technologies have been advocated to meet these challenges, namely: aspect oriented programming (AOP) and reflective middleware. However, these have so far been considered in isolation, or typically target a particular middleware challenge e.g. using aspects to customise a middleware implementation; or using reflection (or dynamic AOP) to alter runtime behaviour. We believe that in combination these technologies better support the engineering of dynamic distributed systems. In this paper, we explore how aspects and reflection have been utilised in both the programming language and middleware communities; building upon this work, we identify four core relationships that form the basis of our model for aspect-oriented reflective middleware. We then explore the potential of this model to i) increase support for the engineering of dynamic reconfigurations, and ii) improve the performance of adaptive systems.

show abstract

Using AOP to Customize a Reflective Middleware

Cited by 2 publications

References 16 publications

Improving modularity of reflective middleware with aspect-oriented programming

Improving modularity of reflective middleware with aspect-oriented programming

The case for aspect-oriented reflective middleware

Contact Info

Product

Resources

About