We have a pretty large codebase from an Eclipse PDE RCP EMF application which we are moving to a web/servlet type application. As part of this effort we are fully moving to run in an OSGI framework and leveraging as much as possible native OSGI approaches like DS. Many of our struggles are surely related to refactoring and using existing libraries, since we can't fully redesigned everything from scratch.
As we start to transform part of the codebase to DS, we are faced with the following cases for which we need to understand best practices. For now we have applied some more traditional approach with service tracker and service reference, but that doesn't feel like the best way to go about it. 1) How to deal with references in classes that are not service and that have constructor arguments (and not basic type supported by config admin) since this can't be turned directly into a component? 2) How to deal with abstract classes that serve as the foundation for a number of other service/component classes and their required references? should those be abstracted in those abstract classes? 3) How to deal with class specialization of a service class. Is that a problem?
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
