On 28.02.2014, at 09:35, Thomas Joseph <[email protected]> wrote:
> What were the design consideration for restricting multiple versions of an > OSGi bundle in the sling tooling - while this is an inherent and > "celebrated" feature natively available in OSGi? There are many use cases > where we would want to have this feature in place, and still use Sling. I think (without having tried multiple versions in practice) this would be rather dangerous in reality. It only makes sense for 3rd party helper libraries - say a logging API or some commons utility. Once you have core API modules of your application with usually singleton services, you really only want a single instance to be running at the same time. Managing different versions of those 3rd party libraries can be nicely done using embedding them in bundles, thus hiding their presence from all the other bundles. This works pretty good. Cheers, Alex
