Hi Nirmal, On Tue, Jun 12, 2012 at 12:05 AM, Nirmal Fernando <[email protected]> wrote: > Hi All, > > We've managed to spawn an EC2 instance via WSO2 LB, using JClouds API, with > few hacks. Though JClouds jars are OSGi bundles, there were few osgi related > issues we under went. > > 1. Installing all required JClouds bundles: Installing them was tedious, > since we have to install all the dependency jars into the carbon server > instance. I had to manually find missing dependencies and install them. > Some how after spending quite a bit of time, I was able to successfully > install and start all the jclouds related bundles. > > 2. JClouds uses Java Service Loader: Java service loader has issues when it > comes to an osgi environment, see [1]. I was able to get rid of those errors > by using Apache Aries- SPI-Fly component, as described in [1]. > But this has some issues like, SPI-Fly should start before APIs and > providers get installed. I guess start level should be able to specify in > Manifest.mf ?
thanks, for introducing the SPI-FLY bundle to dev@ community. Looks promising. But then again i'm not a fan of bundle ordering based solutions. For an example, alll bundles in the carbon server runtime has the start order 4. we can have a local solution for SPI thing based on, bundle fragments (this is the way we used to solve this problem). But then again, in the apache aries site it says, "There are currently standardization efforts ongoing in the OSGi Alliance for which the SPI Fly project is the Reference Implementation" Hence, i think this is the way forward. we may have to revert some bundle start level related hacks in carbon. :) thanks, --Pradeep _______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
