| Re: [equinox-dev] Bundle-ActivationPolicy: lazy without services and Activator |
Thanks Neil
'Bundle-ActivationPolicy: lazy' means that the bundle’s activator will be instantiated and invoked upon the first class loading from that bundle.
If the bundle doesn’t have an activator then nothing will happen. So it is redundant, but I cannot see it having any impact on performance.
Neil
> On 16 Nov 2015, at 22:31, Lars Vogel <lars.vogel@xxxxxxxxxxx> wrote:
>
> Hi,
>
> I typically only set the Bundle-ActivationPolicy: lazy if the plug-in
> provides an service or if I want an Activator to run?
>
> Is there a performance price, if I set the Bundle-ActivationPolicy:
> lazy in Equinox even if the plug-in does not provide any services not
> has an activator?
>
> Best regards, Lars
>
>
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> 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
equinox-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/equinox-dev