Richard S. Hall wrote:
To be very clear, OSGi is not an SOA framework. It promotes a service-oriented interaction pattern for collaboration among modules, since this promotes loose coupling which is good programming practice. But there is nothing in the OSGi framework that relates to Web Services other than the logical concept of a service. As Stuart points out, these concepts in OSGi pre-date web services.
Good point. I think people confuse SOA with web services, or other technologies to implement services (or routing like ESB). But at the very core OSGi is SOA in the best generic sense of the definition. In my view, the most powerful part of OSGi is defining services as
Java interfaces and looking them up dynamically, via filters ,with multiple implementations, etc.