Pryor, J., and Bastn, N.: A Java Meta-level Architecture for the Dynamic Handling of Aspects. In Proceedings of the International Conference on Parallel and Distributed Processing Techniques and Applications, PDPTA'2000, H.R.Arabnia (Ed.). CSREA Press, June 2000.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....performance and optimization issues, and so on. 3. An Aspect Oriented Implementation In order to alleviate the problems of TCS mentioned in the previous section, we addressed separation of concerns by mean of an aspect oriented framework (called Taxonomy AOP) based on a reflective approach [Marcos00, Pryor00, Zunino00]. Taxonomy AOP consists of two levels: a base level where the functional components of the application operate, and a meta level where the aspects and the aspect manager reside. Each application object at the base level may or may not have associated aspects, belonging to the same or different ....

Pryor, J., and Bastn, N.: A Java Meta-level Architecture for the Dynamic Handling of Aspects. In Proceedings of the International Conference on Parallel and Distributed Processing Techniques and Applications, PDPTA'2000, H.R.Arabnia (Ed.). CSREA Press, June 2000.

....the flow graph allows for broad definition of join points. However, AspectJ does not support aspect instantiation or separate compilation. As a result, run time adaptability is not supported. Other feasible approaches to handle dynamic weaving is to implement aspects using meta objects. DJ Aspects [21] is a proposal that addresses dynamic weaving through the use of metaprogramming. Other approaches include the AMF [2, 4, 5] that provides dynamic weaving in a framework. We believe that ideally an implementation should support both static and dynamic weaving. 3.2 Level of weaving and life span ....

Pryor, J., and Bastn, N., "A Java Meta-Level Architecture for the Dynamic Handling of Aspects", Proceedings of PDPTA 2000.

....during requirements engineering and design. Aspects also help to guide component implementation, particularly inter component interface development, and aspect information can be encoded into component implementations for run time use. Unlike most Aspect oriented Programming approaches [20, 21, 22], AOCE avoids the concepts of code weaving and the use of run time reflection mechanisms. Instead we focus on developing components whose cross cutting systemic issues are carefully factored into the component interfaces so that components can be run time re configured and dynamically composed. ....

.... these particular aspects and aspect details by carefully looking at the systemic, cross cutting issues common to many components in our problem domains (visual design tools and Collaborative Information Systems [16] In other problem domains, additional aspects are likely to be necessary (see [20, 40, 13, 22]) For example in real time systems event response time, memory management and concurrency aspects; safety critical systems have redundancy and high assurance aspects; and security critical systems have various additional security related aspects. Developers need to identify the key cross cutting ....

[Article contains additional citation context not shown here]

J.L. Pryor and N.A. Bastan, Java Meta-level Architecture for the Dynamic Handling of Aspects, In Proc. of the 5 th Int. Conf. on Parallel and Distributed Processing Techniques and Applications, Las Vagas (June 26-29 2000), CSREA Press.

No context found.

J.L. Pryor and N,A. Bastan, Java Meta-level Architecture for the Dynamic Handling of Aspects. In Proceedings of the 5 th International Conference on Parallel and Distributed Processing Techniques and Applications, Las Vagas (June 26-29 2000), CSREA Press.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC