ADK_Component - Defining and using components

Components are collections of development resources, which might be transferred between different development databases. ODE provides typical default components for user management, notice system or email features. A component consists of a number of resources collected in an ADK_Component object. Available components are listed in the ADK_Component extent of the ODABA development database (ode.dev) or any other development database providing components.

Providing run-time resources is not the intention of defining components, but rather collection resources for being embedded in another application. Thus, components are usually copied into a development database and adapted to specific project conditions.

Some components might, however be used just as being delivered. Specific requirements for each component is described in the component documentation.

Components consist of several resource object instances which may be copied into another development database. In order not to conflict with resources defined in the target database, global names of component resources always should start with underscore (_) or should be prefixed in another (hopefully) unique way.

When copying component resources, existing resources in the target database will never be overwritten. Depending on the implicit option, only resources explicitly mentioned in the list are copied (implicit false) or referenced resources are copied too (implicit true). The copy rules are described in detail in the following topics.