Eclipse - a tale of two VMs (and many classloaders)

When starting off with Eclipse plugin development or rich client platform development, you're more than likely to run into issues like ClassNotFoundException or problems with the Java command line and properties like java.endorsed.dirs. Most often, these problems arise because many Eclipse developers don't realise the magic that lets Eclipse do its work. Amongst these are the fact that there's actually two processes under the covers, and that each bundle has its own classloader. Once you understand how these fit together, debugging problems may be somewhat easier.

Categories: Platform, OSGi

[html] EclipseZone Article
May 2006
by Alex Blewitt