Hi Peter & Chris, Thanks for the responses.
I think that for my case (where I have full control over A and B) the easiest approach is to merge both into a single Component and use option static reference on the "ClusterService" to decide which functionality to expose. Key part of the use case is to "also stop/cleanup/deactivate the standalone service". This is why service ranking is not a good candidate and lead to me consider the ranking concept for components. The rest of the suggestions assume full control over A and B (which is true for my case), but may not be applicable if A is provided by a 3rd party and I want to provide a clustering extension for it. What would be the ideal approach for this case? (I still have the ability to programmatically deactivate A when B gets activated, but I am not sure if this is ideal). -- Ioannis Canellos _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
