From 825998978663deef743613c0fc703dc99f57daa5 Mon Sep 17 00:00:00 2001 From: venkita Date: Tue, 16 Mar 2004 17:42:57 +0000 Subject: ChangeLogTag: Tue Mar 16 11:22:44 2004 Venkita Subramonian --- TAO/CIAO/ChangeLog | 11 +- TAO/CIAO/docs/index.html | 199 ++++++++++++++----------------- TAO/CIAO/docs/static_ciao_contents.html | 12 +- TAO/CIAO/docs/static_config_example.html | 13 +- 4 files changed, 111 insertions(+), 124 deletions(-) diff --git a/TAO/CIAO/ChangeLog b/TAO/CIAO/ChangeLog index 4f35181b516..9e9f66b7a0f 100644 --- a/TAO/CIAO/ChangeLog +++ b/TAO/CIAO/ChangeLog @@ -1,3 +1,12 @@ +Tue Mar 16 11:22:44 2004 Venkita Subramonian + + * docs/static_ciao_contents.html: + * docs/static_config_example.html: + * docs/index.html: + + Fixed webpage for unnecessary whitespace characters. Fixed links + to images. Thanks to Tao Lu for pointing out. + Tue Mar 16 10:34:41 2004 Jeff Parsons * CIDLC/ServantHeaderGenerator.cpp: @@ -13,7 +22,7 @@ Tue Mar 16 10:36:21 2004 Tao Lu Added the support for CIDL with MPC on Linux. -2004-03-15 Venkita Subramonian +Tue Mar 16 10:52:21 2004 Venkita Subramonian * docs/static_config_example.html: * docs/static_ciao_contents.html: diff --git a/TAO/CIAO/docs/index.html b/TAO/CIAO/docs/index.html index c43fb8a5e1b..0fca2b257c1 100644 --- a/TAO/CIAO/docs/index.html +++ b/TAO/CIAO/docs/index.html @@ -1,133 +1,108 @@ - - - - - - CIAO - Component-Integrated ACE ORB + + +CIAO - Component-Integrated ACE ORB + +

CIAO - Component-Integrated ACE ORB

-

-CIAO - Component-Integrated ACE ORB

+

Introduction

+CIAO is TAO's implementation of CORBA Component +Model (CCM) specially optimized for distributed real-time embedded +(DRE) systems. -

-Introduction

-CIAO is TAO's implementation of CORBA -Component Model (CCM) specially optimized for distributed real-time -embedded (DRE) systems. This page contains links to other documents and +This page contains links to other documents and resources for using CIAO. -

-The CIAO Project

+

The CIAO Project

    -
  • -The main CIAO -project page.
    • - -
      -

      -

  • -Project Status (aka. Release Notes.)
    • - -
      -

      -

  • -This page on implementing new component -explains all the user-defined and tool-generated files when implementing -a component.
    • - -
      -

      -

  • -A list of things that we know need to be done. -:)
    • - -
  • -The Configuration Name/Value lists lists -all the configuration values that CIAO will pass into vaious CCM mechanisms. -The information shown in this page is not visible to CIAO end-users, which -include modeling tool developers. The information that matters for most -users is how these configurations are represented in various XML descriptors -and CIDL specifications.
    • - -
      -

     

- -

-CCM-defined Interface Diagrams

-Here is a set of UML diagrams that we use to figure out the relationship -among all the different interfaces in CCM. You can browse the related part -from the following list: - -
  • -Home and configuration interfaces
    • +

    CCM-defined Interface Diagrams

    + +Here is a set of UML diagrams that we use to figure out the +relationship among all the different interfaces in CCM. You can +browse the related part from the following list: + + +All these diagrams are generating from the CCM.vsd +Visio file (The same file in Visio V.5 format is here.) -
  • -Basic container interfaces
    • +

    CIAO part-by-part

    -
  • -Extended container interfaces
    • +Here is a list of the major parts (I don't want to use the word "component" to confuse you :) of CIAO that a user should be aware of. -
  • -Deployment and installation interfaces
    • - -All these diagrams are generating from the CCM.vsd -Visio file (The same file in Visio V.5 format is here.) -

    -CIAO part-by-part

    -Here is a list of the major parts (I don't want to use the word "component" -to confuse you :) of CIAO that a user should be aware of. -
      -
    • -Daemon: -A CIAO Daemon is the per-host Daemon process which is used to create/spawn -the ComponentServer.
      • - -
    • -ComponentServer: -A ComponentServer is the center part of CIAO. It's responsible for component/home -creation.
      • - -
    • -AssemblyDeployer: -A AssemblyDeployer is responsible for starting the Assembly process.
      • - -
    • -AssemblyManager: -A AssemblyManager is the center part to do the Assembly work.
      • - -
    • -Static Configurator: The CIAO +
        +
      • Daemon: A CIAO Daemon is the per-host Daemon process which is used to create/spawn the ComponentServer.
        • + +
      • ComponentServer: A ComponentServer is the center part of CIAO. It's responsible for component/home creation.
        • + +
      • AssemblyDeployer: A AssemblyDeployer is responsible for starting the Assembly process.
        • + +
      • AssemblyManager: A AssemblyManager is the center part to do the Assembly work.
        • + +
      • Static Configurator: The CIAO Static Configurator acts as a pre-processor that parses the XML descriptor files into intermediate representation that gets linked into the main application. This reduces the initialization time for an application that is statically built. It is mainly aimed at RTOS' like VxWorks that lacks facilities like shared objects or DLL.
        • -
      +
    + + +

    CIAO-tutorials

    -

    -CIAO-tutorials

    We have two Hello tutorials to help the user to understand CCM/CIAO. - - - + + + + + + + + + + + + - diff --git a/TAO/CIAO/docs/static_ciao_contents.html b/TAO/CIAO/docs/static_ciao_contents.html index 5ee1698c08a..6440fab2d82 100755 --- a/TAO/CIAO/docs/static_ciao_contents.html +++ b/TAO/CIAO/docs/static_ciao_contents.html @@ -3,7 +3,7 @@ - + CIAO Static Configuration @@ -57,7 +57,7 @@ them to use only the services available on the target real-time platforms. 2. Current CIAO Configuration Architecture
    -


    +


    Figure 1. Current configuration process in CIAO

    The first stage of the CIAO system lifecycle occurs off-line, when component @@ -87,7 +87,7 @@ information about the component implementations available on that endsystem – each component UUID is mapped to a disk path for the .dll or .so file within which a factory method for its home factory is defined.

    -

    +

    Figure 2. Intermediate representation of configuration information

    The following steps are optional, and will only be performed if they @@ -134,7 +134,7 @@ time (managed by the same project/Makefile processes that do the compilation) into C++ header and source files that are then compiled and linked with the main application.

    -

    +

    Figure 3. Static Configuration in CIAO

    First, one of the generated files is a C++ header file, so that it can @@ -148,7 +148,7 @@ Third, it declares information so that later information depends on earlier information (Figure 4), and the components are directly configured within that header file.

    -

    +

    Figure 4. All XML files are parsed offline and stored as cross-referenced tables in Static_Assembly_Config.h

    @@ -201,7 +201,7 @@ configurations for different system modes).

    -

    +


    Figure 5. CIAO Dynamic vs Static Configuration

    diff --git a/TAO/CIAO/docs/static_config_example.html b/TAO/CIAO/docs/static_config_example.html index fa2a54b0854..25a5989d4dd 100644 --- a/TAO/CIAO/docs/static_config_example.html +++ b/TAO/CIAO/docs/static_config_example.html @@ -3,7 +3,7 @@ - + BasicSP example using CIAO Static Configurator @@ -28,12 +28,15 @@ etc and then establish necessary connections between the components. In the BasicSP example, an external controller  (see $CIAO_ROOT/examples/OEP/BasicSP/README) is used to start or stop a pulser. The generated main driver application (Static_CCM_App.cpp) is modified -to add code to trigger the pulser object on. The generated mpc file is +to add code to trigger the pulser object on. The generated .mpc file is modified to add all other necessary files so that the application can be built statically. -Note that the static configurator only generates only certain files in -the mpc. These filenames are obtained from the XML descriptor files. All -other necessary files have to be added manually as indicated. +Note that the static configurator only generates only certain file names +in the .mpc file. These filenames are obtained from the XML descriptor +files. All other necessary files have to be added manually as indicated. +

    Now the static build files can be generated by running the mpc utility. +

    > cd .. +
    > $ACE_ROOT/bin/mpc -static Static_CCM_App.mpc

    Static_Assembly_Config.h
    #include "Static_Assembly.h"

    #include "CCM_ContainerC.h" -- cgit v1.2.1