Some patterns of component and language integration

Integration is an important concern in many software systems. In this paper, we present a number of patterns that are used to improve the integration of a system with compo-nents or code that is written in dierent languages than the system itself. Component integration is necessary when (foreign) components should be used within a system. The challenge of integrating components into a system is that often heterogeneous kinds of components exist, perhaps without distinct interfaces or other component boundaries. The task of the component integration code is to provide suitable, stable invocation interfaces and to compose the components with the system. Sometimes, however, invo-cation and composition of components is not enough, but a deeper language integration is required. Examples of what might be need are automatic type conversions between languages, preserving the destruction order of the other language, automatic forward-ing of invocations into the other language, and runtime integration of foreign language components. The patterns, presented in this paper, are successful solutions in these ar-eas. Each of these patterns plays an important role in dierent integration architectures. We will give examples from the areas of distributed systems, reengineering projects, scripting languages, and aspect-oriented programming systems. There are many others fields where the patterns are used as well