run_test.pl for more details on how this can be
            done. 
            $(CIAO_ROOT)/tools/Daemon/.  This application
            includes both  ComponentInstallation and
            ServerActivator interfaces.  It also comes
            with a command line utility program to interact with the
            daemon process.  Please see its README file for more
            information.
            Implementation for ComponentInstallation
            interface uses ACE_Configuration to maintain persistency
            of component intallation data. 
It looks like we will have to go straight to our planned 0.2 release as our first publically available CIAO.
| Modules | Status | 
|---|---|
| CCM Core | We are currently working on a prototype that enables remote
        component installation using the CCM ComponentInstallationinterface, a component
        server implementation.  Since we
        still don't have a CIDL implementation, we will also write up
        an example to show how the code should be generated in both
        CCIDL compiler and provide example component
        implementations.
        There exists 3 libraries in CCM Core.
 | 
| TAO_IDL | TAO_IDL has been extended to handle and generate all the
        component related keywords but import.  We are
        currently using the generated mapping, in combination to
        manually simulation of CIDL generated code to implement CCM
        component.
        TAO_IDL Check out  TAO IDL compiler for more details. | 
| CIDL (Component Implementation Defintion Language) Compiler | An implementation that supports a subset of CIDL appropriate for
		DRE systems has been implemented.
        We do not have immediate plans to integrate
        Persistence State Service into the CIAO CIDL compiler. At present
        we support only a simple construct like the following: 
        module component_composite_name {
          composition service component_home_executor {
            implements component_home;
            manages component_executor;
          };
        };
The compiler generates operation implementations
        inherited from following interfaces:
 | 
Components module namespace if not specified explicitly.
            
              - Navigations
              
- Receptacles
              
- Events
            
            interfaces and their supporting data types that
            CCMObject interface requires.  These
            interfaces are defined in 
            CIAO_Base.pidl
            and CIAO_Event.pidl.
        
            
              - CCMObject
              
- CCMHome
              
- KeylessCCMHome
            
 and their supporting data types as defined in part
            of the 
            CIAO_Component.pidl .
        
            
              - CCMContext, SessionContext
              
- EnterpriseComponent, SessionComponent
            
        CORBA::LocalObject interface has been
                  added a long time ago.
              get_component() method in
                  CORBA::{Object|LocalObject}
                  interfaces.
            HomeExecutorBase interface
        Deployment module.
            
      
HomeFinder interface
        HomeRegistration interface
        
            
              - Configurator
              
- StandardConfigurator
              
- HomeConfiguration
            
        
            
              - EntityContext
              
- EntityComponent
            
        Navigations, Receptacles,
                  and Events interfaces of a components
              Deployment implementation, assuming
            the revised deployment specification will be available
            
      
SessionSynchronization and other
            interfaces in Transaction module, assuming
            time permitting  and
             XOTS  will be
            available in April 2003 timeframe
        CCM2Context, Session2Context, Entity2Context
            and 
        - Support for ExecutorLocatorbased component
            implementation
- ProxyHomeRegistrationinterface