iPOJO Future Ideas

This page documents various ideas to be considered in the future, but not currently on the road map.

Service Property Injection

Access to service properties is sometimes necessary to gain access to service configuration or as a way to defer service object creation. Currently, the only way to access service properties is via a service callback method that accepts a ServiceReference object. The downside of this approach is that it ties your component to the OSGi API. Other possibilities include adding support for:

1. Service callback methods with a Map parameter that accepts the service properties.
2. Service property injection into component fields.

Extender Model Support

iPOJO was designed to support the OSGi service model, but the extender model is another approach that can be used on top of the OSGi framework. Instead of listening for service events, the extender model listens for bundle events and then probes bundles to determine if they provide specific extensions. It would be beneficial if iPOJO could somehow be enhanced to support the extender model too.

For example, iPOJO could define a simple declarative way for extension providers to declare the extensions they provide and a way for extension consumers to declare the extensions they require. For example, the actual extensions could be properties, resources, or classes and they could be injected into array fields into the consumer. A set of iPOJO handlers could be created to support these mechanisms.