Dashboard > UDIG Developer Guide > Home > 2 Programmers Guide > 3 Working with Plugins > 7 Plugin Classloader Use
7 Plugin Classloader Use Log In | Sign Up   View a printable version of the current page.

Added by jeichar@refractions.net , last edited by Jody Garnett on Jun 21, 2007  (view change)
Labels: 
(None)

Eclipse's Classloader maintains seperate classpaths for each plugin.

A plugin's classpath is derived from its parents classpath and the plugin dependencies. It must be realized that the classpath a plugin has access to is not the same classpath as the environment provides. For example a java application has a different class path than a plugin.

You can configure your classpath stuff in your Manifest:

  parentClassloader=app The application class loader
  parentClassloader=boot Your plugin can just see JRE classes (ie the boot classpath)
parentClassloader=ext Your plugin can see JRE and JRE extention classes - such as JAI and ImageIO

As noted above - the difficulty with default classloader configuration is that it does not recognize java extensions such as JAI because the jai jar files are in the jre/lib/ext directory.

For more information please consult the Eclipse Help menu.

Powered by a free Atlassian Confluence Open Source Project License granted to uDig. Evaluate Confluence today.
Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators
User-friendly Desktop Internet GIS