Be the first to like this
OSGi DevCon 2008
Class.forName and ClassLoader.loadClass seem to be synonyms for the same basic operation: request a dynamic class load. Yet calling Class.forName does additional "checking" which is not very useful (certainly in OSGi). Class.forName does certain loader constraint checks to ensure type safety which are not necessary when doing dynamic class loads. This short talk will explore this issue and discuss a proposed "hack" to work around the issue for legacy code which can't easily be changed to avoid Class.forName.