APAM/Concepts

From Wiki Adele Team
< APAM
Revision as of 09:16, 12 October 2011 by Jacky (talk | contribs) (Created page with 'The Apam system is made of the Apam (APplication Abstract Machine) platform, and a number of managers that, collectively, are designed for the run-time support of dynamic applica…')

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

The Apam system is made of the Apam (APplication Abstract Machine) platform, and a number of managers that, collectively, are designed for the run-time support of dynamic applications.

The Apam system is based a component-service metamodel which goal is the run-time support and control of applications whose behavior ranges from "classic" components platforms (like in EJB, Fractal, ...), to "pure" service platforms (like OSGi, SCA, webService , ...). The Apam platform manages the current state of the supported applications (called ASM for Application State Model) as a model conforming to the component-service metamodel. The Apam platform provides an API for the management of this ASM, mechanisms for enforcing the declared component behavior, and mechanism for extending the system through the addition of specialized “managers”. The following only describes the Apam platform.

The Apam metamodel emphasizes the concepts of specification, implementation and instances.


Specification concept

A specification is a first class object that defines a set of provided “interfaces” and a set of required specifications.

Implementation concept

dqfgqefg