0 Replies Latest reply on Aug 9, 2010 7:11 AM by thomas.diesler

    XService initial implementation and direction

    thomas.diesler

      XService is the ability to integrate OSGi services with non-OSGi services that exist in the same runtime (i.e. JBossAS). This effort was known as 'servicemix' in the Microcontainer based Framework. We decided to use a different working name because folks would frequently get confused with the Apache ESB that is developed under the name Apache ServiceMix.

       

      We currently support the ability for:

       

      * OSGi Bundle dependens on a Module (and vice versa)

      * OSGi Service accesses MSC Service (and vice versa)

       

      See ModuleDependencyTestCase and ModuleServiceTestCase for details and test coverage. This functionality is the foundation for successful integration of various component models in AS7 with OSGi (and vice versa). Every OSGi Bundle is an AS7 Module, but not every AS7 Module is also an OSGi Bundle. Every OSGi Service is an MSC Service, but not every MSC Service is also an OSGi Service.

       

      It turns out that Modules does currently not define adequate meta data descriptors to describe their OSGi exposure. We used modules.xml for the above tests, but this is not the intended way to go forward as described in MODULES-20 and its related forum post.

       

      To be continued ...