ASCoDT Component Lifecycle

From Sccswiki
Revision as of 11:44, 13 September 2012 by Atanasoa (talk | contribs)
Jump to navigation Jump to search

ASCoDT covers the full component lifecycle, consisting from component development, component testing, component instantiation and exporting of components. For the development of new component or components instantiation one needs an ASCoDT Project.

The ASCoDT Project

The ASCoDT is used the organise the different source files and binaries needed to compile and run a component-based application.

Project creation

The ASCoDT project can be created through separate new project wizard available through the context menus of the project expoler, navigator or through the File->New->Project menu. The ASCoDT compiler is attached to the project. Additionally the project includes the java run time libraries and can be extended with further jar files.

Project structure

The project structure can be separated in physical and logical structure.

Physical structure

The physical structure of the project includes all source files, binaries, files needed for the storage of the logical structure and dependent libraries or ASCoDT_SIDL sidl files. The following table corresponds to the initial physical setup of the ASCoDT project:

Path Description
sidl for the storage of component sidl files
src for the storage of the generated blue-prints needed to be implemented by the user
component for storage of stubs
workspace for the storage of dynamic repositories

Logical structure

Logically the ASCoDT project consist from one static and multiple dynamic repositories.

  • Static repository: corresponds the definitions of interfaces and components as classes. The static repository is computed every time the project is loaded though the sidl files defined locally in the project and there dependencies. After change of the sidl the static repository becomes non valid. A recompilation of the repositories should be triggered through the Project->Build repositories
  • Dynamic repository: corresponds to the actual workbench setup - instances of components and ports. The dynamic repository is serialized by save to files

Defining new component

Component instantiation

Exporting components