Apache Felix iPOJO Feature Overview

This page is an attempt to put all of the features and benefits of iPOJO into a single high-level list so that it is easy to see why you will want to use iPOJO for your applications.

• POJO-based approach - Most components can simply be POJOs and need not have an iPOJO- or OSGi-specific API in them.
• Rich service dependency management - Automatically manages a full spectrum of service dependencies.
  • Optional or mandatory service dependencies.
  • Singular or aggregate service dependencies.
  • Member field injection and/or binding method injection.
  • Support for various "binding policies".
    • Static dependencies cannot change without invalidating the component instance, so injected services typically do not change at run time and service departures typically result in the component instance being destroyed and potentially recreated. (coming soon)
    • Dynamic dependencies can change without invalidating the component instance, so injected services can change at run time, but are static with respect to service priority changes (i.e., they do not automatically switch if a higher priority service appears).
    • Dynamic priority dependencies can change without invalidating the component instance and do dynamically update based on service priority rankings at run time. (coming soon)