A component is a configured instance of an implementation. The services provided and consumed and the available configuration properties are defined by the implementation (represented by its componentType).
Every component has a name which uniquely identifies it within the scope of the composite that contains it; the name must be different from the names of all other components, services and references immediately contained in the composite (directly or through an <include> element).
A component may define a {@link PropertyValue} that overrides the default value of a {@link Property}defined in the componentType.
It may also define a {@link ReferenceTarget} for a {@link ReferenceDefinition} defined in the componentType.The ReferenceTarget must resolve to another component or a reference in the enclosing composite.
Components may specify an initialization level that will determine the order in which it will be eagerly initialized relative to other components from the enclosing composite that are in the same scope. This can be used to define a startup sequence for components that are otherwise independent. Any initialization required to resolve references between components will override this initialization order.
@version $Rev: 430937 $ $Date: 2006-08-11 18:17:56 -0700 (Fri, 11 Aug 2006) $
|
|
|
|