Unfortunately the eclipse extension registry assumes a flat space for bundles and depends on the bundles providing extensions to be singletons. With that in mind the only way I can see this working is if the equinox extension registry is installed into each isolated region such that each installation of the extension registry can only see the bundles within its corresponding region.
Tom From: Florian Pirchner <[email protected]> To: [email protected] Date: 10/15/2015 11:00 AM Subject: [equinox-dev] Regions and Extension-Registry Sent by: [email protected] Hi, i got a question about the combination of regions and the extension-registry. In my scenario i will have 2 separated regions. Lets call them A and B. Additionally there are 2 bundles for each region: Bundle-A-provider - Is added to region A and provides an equinox-extension with ID=foo Bundle-A-consumer - Is added to region A and consumes an equinox-extension with ID=foo Bundle-B-provider - Is added to region B and provides an equinox-extension with ID=foo Bundle-B-consumer - Is added to region B and consumes an equinox-extension with ID=foo My question: Can equinox-registry deal with this use case? So will equinox ensure, that the provided extension from Bundle-A-provider is only consumeable by Bundle-A-consumer? Or will the extension from this provider also become used by Bundle-B-consumer? Thanks, Florian_______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________ equinox-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
