Page History

...

• Composite model - iPOJO supports a flexible architectural-like model for composing services.
  • Flexible composites - A composite is an abstract component implementation.
    • Sub-services and sub-components - Unlike traditional component composition, an iPOJO composite can be described in terms of services in addition to sub-components; thus sub-service implementation selection is deferred until run time.
    • Optional/mandatory sub-services and/or sub-components.
    • Singular/aggregate sub-services and/or sub-components.
  • Hierarchical - A composite component may contain other composite components.
    • Composite scoping - A composite acts as a scoping mechanism where sub-services/sub-components are not visible externally and external services are not visible internally.
  • Service dependencies - A composite has the full expressive capabilities of primitive components when it comes to service dependencies (see above description of service dependencies in core features).
    • For a composite, a service dependency effectively imports an external service into the composite scope from its parent composite (which may be the OSGi service registry in the root case).