I'm not an expert on this, but it doesn't
sound like the desired behaviour. I think the bundle should only
be activated when a class is actually loaded from it. I suggest entering
a bug report against Equinox Framework.
<tom.huybrechts@xxxxxxxxx> Sent by: equinox-dev-bounces@xxxxxxxxxxx
30/07/2006 02:12 PM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
"Equinox development mailing list"
If a bundle does buddy classloading, then the classloading magic will
try to load the requested class from each bundle in a given set (all,
dependent, registered, ...). If any of these bundles has a
Eclipse-AutoStart header they will be started, even if they don't have
that class. In the worst case, with a global buddy policy and a
non-existent class, every AutoStart bundle will be activated.
Is this intended behaviour, or should these bundles only be started
when a class is really loaded ?
equinox-dev mailing list