Use the K2 CIDL compiler to generate CORBA 2.x IDL from CORBA 3.0 idl. Refer to the Programmer’s Guide for usage details.

Use the K2 CIDL compiler to generate C++ CIF Implementation code from Composition declarations. Refer to the Programmer’s Guide for usage details.

CORBA Component Descriptor (CCD), describes the Component properties such as Transaction requirements, Security requirements, Persistence and Database Mappings. It allows the Component to configured after Development, during the Deployment phase. CORBA Softpackage Descriptor (CSD), provides the implementation details of a Component and external dependencies it may have. It can be used to describe and provide multiple implementations using different platforms and programming languages. These files can be generated automatically using the - -gen-desc option of the k2cidl compiler while compiling a .cidl file (refer to Programming Manual for details on options of k2cidl compiler). Both CSD and CCD form part of the Deployable unit for the Component.

Entity component can be developed using either component managed persistence or container managed persistence.Both examples are provided in k2/examples/ccm/basic/entity directory. Component managed persistence can be written using ODBC/OTL/Pro*C/PSS without container support for connections and transaction management. Container Manager Persistence is supported for basic session only i.e. no transactional session. We are planning to implement subset of OTS specification for connection support and transaction propagation of transactional context that may be integrated with third party OTS for distributed transactions.

Yes. You must set your PATH correctly before starting up K2 servers in order to load MFC DLL during runtime. Also you can specify third party DLL dependencies using dependency tag in soft package descriptor (.csd). This dependency can be specified as a link or archive file contained in the CORBA component package.

Yes.Please refer the link for setting up workspace.

You need to compile your components using debug option, package them (.zip) and finally deploy into CCM container hosted in CCM Server. During runtime you can attach specific CCM Server (ccmserv.exe) to the debugger.

It’s partially supported. K2 supports standard CCM deployment model to install, update and uninstall packaged on a node or a cluster. Our design is based on Component Repository to view, modify and query components or packages. The update functionality is meant to achieve version control on component binaries, which is not supported yet.

In basic component model, for making connection to another component you have to program explicitly during activation of component. So far this is not flexible approach for dynamic re-configuration. Extended component solves this problem by exposing component facets and receptacle. Using IDL compiler you can generate equivalent IDL for receptacles that generates operations for connecting and disconnecting components. Using CIDL compiler you can generate component implementation that implements the equivalent operations of receptacle. Making connection is an agent's responsibility that creates component instances.

• 
• Developing in OMG's new MDA
  by Jon Seigel
  Director, Technology Transfer, OMG