2009/4/8 Simon Laws <[email protected]>: > Hi Ram > > snip... > >> A SCA OSGi Binding can enable interworking between SCA components and OSGi >> services > > I'd like to understand the scenario in a little more detail. Do you > mean here that an SCA component and a Non-SCA OSGi based service will > be interacting within the same JVM? > > Simon >
My understanding of binding.osgi is that is what it does. The OSGi service implementations live in the same JVM, but are outside the management of SCA. This, for me, makes it seem like a slightly strange binding (from an SCA perspective), but it may make sense from an OSGi-centric perspective. I think it's worth noting that we should be able to achieve the two interoperability use cases described through implementation.osgi, the difference being SCA would be responsible for the lifecycle of the bundles. If binding.osgi does go ahead we should make sure the information described to configure the bindings (to map between OSGi and SCA services) is consistent with that described for implementation.osgi, since both would be configuring the same mappings. Regards, Graham.
