Hi Rajini, good to hear that you're going to contribute to SCA-OSGi :-)
We wrote a paper about the different possibilities of combining OSGi and SCA for the SCA drumbeat end of march. You can find it on the OSOA homepage: http://www.osoa.org/display/Main/SCA+Resources. The paper contains a high level description of the OSGi Binding, implementation type and OSGi host. Would be great to get some comments from you. >If there are references from the OSGi component to other non-OSGi SCA >components, a proxy service is registered by the Tuscany runtime with the >OSGi registry so that the OSGi bundles can access these SCA services as >normal OSGi services. Well, this is one option, but not the only one. If for example the non-OSGi SCA component provides a SOAP service binding, a SOAP proxy will be injected. >References from non-OSGi components to OSGi components >are resolved by looking up the OSGi registry. Yes, if the non-OSGi SCA component has declared a reference with OSGi binding. If the OSGi component has declared a JMS service binding, the non-OSGi SCA component could use JMS instead of OSGi binding :-) Best regards Nicole > >Hello, > > >I would like to contribute to the SCA<->OSGi integration activities. > > >I have been looking at the existing OSGi binding implementation in > Tuscany > >which exposes SCA services as OSGi services. Even though this binding > is no > >longer working with the latest Tuscany builds, the samples were very > useful > >to understand the scenarios. I was also looking at the notes on the > mailing > >list (they are slightly old - dated Nov 2006) which talk about an > OSGi host > >and also an OSGi implementation type. Is there any ongoing work in > these > >areas? > > >Graham Charters and I have been investigating the use of an OSGi > >implementation type which will enable existing OSGi bundles to be run > as SCA > >components under Tuscany. We are particulary interested in the > scenario > >where Tuscany is in control. If components of OSGi implementation > type are > >specified in the composite, Tuscany starts up an OSGi runtime and > deploys > >the OSGi bundles corresponding to the components into the OSGi > runtime. If > >there are references from the OSGi component to other non-OSGi SCA > >components, a proxy service is registered by the Tuscany runtime with > the > >OSGi registry so that the OSGi bundles can access these SCA services > as > >normal OSGi services. References from non-OSGi components to OSGi > components > >are resolved by looking up the OSGi registry. > > >We would like to obtain feedback on using this approach and also > would like > >to get involved in the ongoing support for SCA<->OSGi integration. > > >Thank you... > > > >Regards, > > >Rajini >
