Describing and using non functional aspects in component based applications

ABSTRACT

One of the major progress due to component based technology is the capability to let the "infrastructure" manage some (non functional or extra functional) aspects such as persistency, distribution and so on without having to change the application code, using a wrappers technology (containers). Aspect Oriented Programming (AOP) is a technology that provides a language in which different aspects can be applied to an application using a technology that "weaves" the code implementing the aspect inside the application code.Both technologies are addressing the same "separation of concerns" issue, but containers propose only a fixed set of services, while AOP require the capability to change the component code, and is working at the object level.In our work, we merge both approaches, allowing aspect designers to define new aspects or services and aspect users to apply these aspects or services on components without the component code availability. This goal is reached by providing two languages, one for aspect designers the other one for aspect users, and by using a palette of technologies including object (stub) generation, method call interception and run-time instrumentation.

REFERENCES

• 1: Mehmet Aksit , Lodewijk Bergmans , Sinan Vural, An Object-Oriented Language-Database Integration Model: The Composition-Filters Approach, Proceedings of the European Conference on Object-Oriented Programming, p.372-395, June 29-July 03, 1992
• 2: AspectJ Home Page http://aspectj.org
• 3: B. Bokowski, A. Spiegel. Barat, A Front End for Java Institut für Informatik Freie Universität Berlin, 1998
• 4: N. M. N. Bouraqadi-Saâdani, T. Ledoux. Le point sur la programmation par aspects. In Techniques et sciences informatiques Volume 20 --- n°4/2001, pages 505-528
• 5: N. M. N. Bouraqadi-Saâdani. Un MOP Smalltalk pour l'étude de la composition et de la compatibilite des métaclasse. Application à la programmation par aspects. Phd Thesis, Ecole des mines de Nantes, July 1999
• 6: Shigeru Chiba, Load-Time Structural Reflection in Java, Proceedings of the 14th European Conference on Object-Oriented Programming, p.313-336, June 12-16, 2000
• 7: Corba Component Model http://www.omg.org
• 8: K. Czarnecki, U. W. Eisenecker, and P. Steyaert. Beyond Objects: Generative Programming. A position paper for the ECOOP'97 Workshop on Aspect-Oriented Programming, Jyväskylä, Finland, June 10, 1996
• 9: Dassault Systèmes http://www.dassault-systemes.com/
• 10: DemeterJ www.ccs.neu.edu/research/demeter/releases/
• 11: F. Duclos, J. Estublier, R. Sanlaville. Architectures Ouvertes pour l'Adaptation des Logiciels. In Proceedings of ICSSEA00, Paris
• 12: J. M. Favre, F. Duclos, J. Estublier, R. Sanlaville, J.J Auffret. Describing and Supporting an Industrial Software Component Model. In Proceedings of 5th European Conference on Software Maintenance and Reengineering. CSMR 2001. Germany.
• 13: E. Gamma, R. Helm, R. Johnson, J. Vlissides. Design Patterns. Addison-Wesley, 1995
• 14: Mohamed G. Gouda , Ted Herman, Adaptive Programming, IEEE Transactions on Software Engineering, v.17 n.9, p.911-921, September 1991 [doi>10.1109/32.92911]
• 15: Steven D. Gray , Roger Jennings, Microsoft Transaction Server: Roger Jennings' Database Workshop with Cdrom, Sams, Indianapolis, IN, 1997
• 16: IBM HyperJ www.alphaworks.ibm.com/tech/hyperJ
• 17: IBM Multi-Dimentional Separation Of Concerns, www.research.ibm.com/hyperspace
• 18: Inside COM+, Microsoft Press
• 19: J2EE http://java.sun.com/Java
• 20: Java Tech Tips 04-2000 http://developer.java.sun.com/developer/TechTips/2000/tt0530.html
• 21: JONAS http://www.objectweb.org
• 22: Gregor Kiczales , Jim Des Rivieres, The Art of the Metaobject Protocol, MIT Press, Cambridge, MA, 1991
• 23: Kiczales, G., et al. Aspect-Oriented Programming. In Proceedings of the European Conference on Object-Oriented Programming (ECOOP). Vol. LNCS 1241. Springer-Verlag, June 1997.
• 24: Y. Ledru, R. Sanlaville and J. Estublier. Defining an Architecture Description Language for Dassault Systèmes. In B. Balzer and Henk Obbink, editors, Proceedings of the 4th International Software Architecture Workshop (ISAW4), pages 115-120, Limerick, Ireland, June 2000.
• 25: Lopes C. V. and Hursch W. L. Separation of Concerns. College of Computer Science, Northeastern University, Boston, February 1995
• 26: Remy Sanlaville, Jean-Marie Favre and Yves Ledru. Helping Various Stakeholders to Understand a Very Large Component-Based Software. Euromicro Workshop on Component-Based Software Engineering. Warsaw, Poland. September 4 - 6, 2001. (I8/35)
• 27: Sun Microsystems Enterprise JavaBeans TM Specification, Version 2.0 September 2000

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.2 Design Tools and Techniques

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.3 Coding Tools and Techniques
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications
          Subjects: Design languages

General Terms:
Design, Languages

Keywords:
component, component based software engineering, component framework, component model, container, generative programming, non-functional or extra functional aspect