Re: [gemini-dev] switch for blueprint support

[Glyn Normington <gnormington@xxxxxxxxxx>]

Thanks Andrew. Further discussion will take place in the bug.

Regards,
Glyn

On 22 Apr 2013, at 21:46, Andrew Clemons <andrewclemons@xxxxxxxxxxx> wrote:

> Glyn,
> 
> On 2013-04-22 09:09:01 +0100, Glyn Normington wrote:
>> Thanks for this Andrew.
>> 
>> There is a design issue with multiple extenders competing to extend a
>> particular application bundle. The OSGi Alliance is defining some
>> standard generic capabilities that extenders can provide and
>> applications can require so that an application can say that it needs
>> a particular extender, although I'm not sure that much thought has
>> been given to selecting between distinct implementations of the same
>> extender standard. I'll mention this use case
>> So your patch is probably a necessary evil. ;-)
> 
> Great, thanks for that.
> 
>> Please could you raise a bug and attach the patch. ChainActivator
>> seems like a reasonable spot for the new logic.
> 
> This is the ticket:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=406255
> 
>> Your patch would also be useful in scenarios where Gemini Blueprint
>> and Aries Blueprint need to co-exist, such as when running Aries
>> Subsystems in Virgo ([1]).
> 
> Just having a look at this now.
> 
> _______________________________________________
> gemini-dev mailing list
> gemini-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gemini-dev