Hi Gareth, I think that it doesn't matter who initializes the instance. It matters though who creates the Hazelcast collection (Set,List,Map etc). So I think that the best approach is to reuse cellar's hazelcast instance which is exported as a service.
I really don't understand why these scenarios fail for you. I reused the code you posted in your previous example and it worked fine (that was scenario 1). I've created a sample of a hazelcast application that reuses the cellar hazelcast instance (imports it as an OSGi service). You can have a look of that sample at: https://svn.apache.org/repos/asf/karaf/cellar/trunk/samples/hazelcast-app/. I wonder if the reason that makes this sample work is the fact that cellar-hazelcast has a dynamic-import on org.apache.karaf.cellar.* packages. I will try changing the package name and see if it still works. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf <http://karaf.apache.org/> Committer & PMC Apache ServiceMix <http://servicemix.apache.org/> Committer Apache Gora <http://incubator.apache.org/gora/> Committer *
