[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Checking whether a class is available in the target platform

What is the bug number where the revert happened and we can discuss the alternatives?

If you want to avoid lazy activation of the bundle then we have to avoid actually loading the class in the check.  I think you may be able to try locating the .class resource instead of actually trying to load the class with the bundle class loader.


From:        Simon Scholz <simon.scholz@xxxxxxxxxxx>
To:        equinox-dev@xxxxxxxxxxx
Date:        10/07/2015 05:14 AM
Subject:        [equinox-dev] Checking whether a class is available in the target        platform
Sent by:        equinox-dev-bounces@xxxxxxxxxxx


we are currently facing problems, when trying to figure out if a class
is available in the target platform or not.
So in case certain bundles are removed from the target platform the E4
application model should be cleaned up accordingly, which means that
referenced model objects, should be removed from the E4 application
model, if the contributing bundle is not available any more.

Thomas Watson suggested this solution
https://bugs.eclipse.org/bugs/show_bug.cgi?id=445663#c4, which
unfortunately causes the bundles to load.
This is undesired and therefore this patch has been reverted:

So is it somehow possible to figure out if a certain class is available,
when we have the Bundle-SymbolicName and the full qualified classname,
without activating/loading the bundle?

Thanks in advance and regards,


Trainer, Consultant and Developer

vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Tel (040) 78804360, Fax (032) 221739404, Email: simon.scholz@xxxxxxxxxxx, Web:

equinox-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit