PacoSuite and JAsCo: A Visual Component Composition Environment with Advanced Aspect Separation Features

Vanderperren, Wim; Suvee, Davy; Wydaeghe, Bart; Jonckers, Viviane

doi:10.1007/3-540-36578-8_12

Cited by 5 publications

(3 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, AWED [2] is an aspect-oriented programming language that features explicit distribution. It is built on top of JAsCo [33], a system that provides dynamic aspects for Java. Aspects are represented as plain Java objects that can be dynamically deployed.…”

Section: Discussion and Related Workmentioning

confidence: 99%

Augmenting reflective middleware with an aspect orientation support layer

Surajbali

Coulson

Greenwood

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

Reflective middleware provides an effective way to support adaptation in distributed systems. However, as distributed systems become increasingly complex, certain drawbacks of the reflective middleware approach are becoming evident. In particular, reflective APIs are found to impose a steep learning curve, and to place too much expressive power in the hands of developers. Recently, researchers in the field of Aspect-Oriented Programming (AOP) have argued that 'dynamic aspects' show promise in alleviating these drawbacks. In this paper, we report on work that attempts to combine the reflective middleware and AOP approaches. We build an AOP support layer on top of an underlying reflective middleware substrate in such a way that it can be dynamically deployed/undeployed where and when required, and imposes no overhead when it is not used. Our AOP approach involves aspects that can be dynamically (un)weaved across a distributed system on the basis of pointcut expressions that are inherently distributed in nature, and it supports the composition of advice that is remote from the advised joinpoint. An overall goal of the work is to effectively combine reflective middleware and AOP in a way that maximises the benefits and minimises the drawbacks of each.

show abstract

Section: Discussion and Related Workmentioning

confidence: 99%

Augmenting reflective middleware with an aspect orientation support layer

Surajbali

Coulson

Greenwood

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

show abstract

“…Secondly, it needs to propagate the relevant join points on Witness as required join points on Person. This is achieved by around advice that calls proceed and additionally calls the appropriate methods (lines [17][18][19][20][21]. Because there is a mismatch in the sense that Person has separate concepts for first name and last name, extra mapping functionality is required.…”

Section: Listing 1 Example Implementation Of the Adaptermentioning

confidence: 99%

“…AWED [3] supports dynamic weaving of aspects using the DJAsCo [20] distributed AOP architecture. It supports the weaving of stateful distributed aspects, and through the use of a consistency protocol ensures that whenever an aspect is woven at a specific host, mirrors are also woven at other involved hosts.…”

Section: Related Workmentioning

confidence: 99%

Proceedings of the 6th workshop on Aspects, components, and patterns for infrastructure software

2007

View full text Add to dashboard Cite

Bibliografische Information der Deutschen NationalbibliothekDie Deutsche Nationalbibliothek verzeichnet diese Publikation in der Deutschen Nationalbibliografie; detaillierte bibliografische Daten sind im Internet über http://dnb.d-nb.de abrufbar. Aspect oriented programming, component models, and design patterns are modern and actively evolving techniques for improving the modularization of complex software. In particular, these techniques hold great promise for the development of "systems infrastructure" software, e. g., application servers, middleware, virtual machines, compilers, operating systems, and other software that provides general services for higher-level applications. The developers of infrastructure software are faced with increasing demands from application programmers needing higher-level support for application development. Meeting these demands requires careful use of software modularization techniques, since infrastructural concerns are notoriously hard to modularize. UniversitätsverlagAspects, components, and patterns provide very different means to deal with infrastructure software, but despite their differences, they have much in common. For instance, component models try to free the developer from the need to deal directly with services like security or transactions. These are primary examples of crosscutting concerns, and modularizing such concerns are the main target of aspect-oriented languages. Similarly, design patterns like Visitor and Interceptor facilitate the clean modularization of otherwise tangled concerns.Building on the ACP4IS meetings at AOSD 2002-2009, ACP4IS '10 aims to provide a highly interactive forum for researchers and developers to discuss the application of and relationships between aspects, components, and patterns within modern infrastructure software. The goal is to put aspects, components, and patterns into a common reference frame and to build connections between the software engineering and systems communities. Scope of the WorkshopThe importance of "systems infrastructure" software-including application servers, virtual machines, middleware, compilers, and operating systems-is increasing as application programmers demand better and higher-level support for software development. Vendors that provide superior support for application development have a competitive advantage. The software industry as a whole benefits from an increased base level of abstraction, decreasing the need for application programmers to continually "reinvent the wheel".These trends, however, mean that the demands on infrastructure software are increasing. More and more features and requirements are being "pushed down" into the 1 infrastructure, and the developers of systems software need better tools and techniques for handling these increased demands. The design and implementation of systems-level software presents unique opportunities and challenges for AOSD techniques. These challenges include the need to address the inherent complexity of infrastructure software, the need for strong a...

show abstract