Scott, I think that for the older frameworks, registering the service against the API bundle (i.e. the exporter) is probably the best compromise.
It does limit the RSA provider to supporting only one version of the service interfaces in case there are multiple, but this feels like a reasonable trade off: multiple exports of an interface should be the exception rather than the rule. Also the service appears to be coming directly from the API bundle, so perhaps attach a property to make it clear what is going on. DynamicImport-Package just gives you too little control in my opinion. Cheers, Neil On Tue, Feb 22, 2011 at 11:17 PM, Scott Lewis <[email protected]> wrote: > I'm happy to report that our new 'static dummy bundle' for RSA proxy > ServiceFactory registration seems to work on Equinox 3.7m4 (yay!). > > I still need to test on recent Felix (which should be pretty easy once our > builder is finished...i.e. we have/create a maven repo that can be used to > run on Felix created by our build system [1], but it will take some time to > complete the build/autotest/deploy/etc). > > Thanks to Neil, BJ, Richard, Peter, Thomas and others for the explanation, > investigation, and example code. It's appreciated. > > If anyone out there have any suggestions with supporting older versions of > Equinox (i.e. before 3.7m3) wrt the proxy ServiceFactory, please say so. My > initial inclination is to use Dynamic-ImportPackage: * in the current TM > bundle...and accept it's limitations WRT service type versioning...as the RI > has apparently done. If there are better strategies floating around please > let me know. > > Thanks, > > Scott > > [1] http://download.ecf-project.org/maven/ > [2] ECF builder: https://build.ecf-project.org/jenkins/ > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
